Fix parsing of exact-length JSON with a UTF-8 BOM - #1077
Open
Sn0wyDay wants to merge 1 commit into
Open
Conversation
Sn0wyDay
force-pushed
the
fix-exact-length-utf8-bom
branch
from
September 12, 2026 17:06
faddc35 to
5eac121
Compare
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.
cJSON_ParseWithLength()rejects a valid four-byte, non-NUL-terminatedbuffer containing a UTF-8 BOM followed by
0(EF BB BF 30).skip_utf8_bom()currently requires index 4 to be accessible before itcompares the three-byte BOM. This changes the bound to index 2, the last byte
read by
strncmp(), and adds an exact-length regression test.Validation:
git diff --checkpasses.