fix: the vendored flatcc portable header pstdint in pstdint.h#887
Open
orbisai0security wants to merge 1 commit into
Open
fix: the vendored flatcc portable header pstdint in pstdint.h#887orbisai0security wants to merge 1 commit into
orbisai0security wants to merge 1 commit into
Conversation
Automated security fix generated by Orbis Security AI
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fix high severity security issue in
thirdparty/flatcc/include/flatcc/portable/pstdint.h.Vulnerability
V-001thirdparty/flatcc/include/flatcc/portable/pstdint.h:833Description: The vendored flatcc portable header pstdint.h uses unbounded sprintf() calls to format integer values (including INT64 and UINT64 maximum values) into fixed-size stack buffers str0 and str1. No maximum output length is specified in any of the nine sprintf calls. If the fixed-size buffers are smaller than the maximum formatted representation of INT64/UINT64 values (up to 20 decimal digits plus sign and null terminator = 22 bytes minimum), a stack buffer overflow occurs at library initialization time. This is a latent code defect in vendored code rather than a directly injectable attack, but represents a real memory safety risk.
Changes
thirdparty/flatcc/include/flatcc/portable/pstdint.hVerification
Automated security fix by OrbisAI Security