Guard memcpy against NULL when storing an empty string value#14
Open
SAY-5 wants to merge 1 commit into
Open
Conversation
Signed-off-by: Sai Asish Y <say.apm35@gmail.com>
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.
Parsing valid JSON with an empty object key (e.g.
{"":1}) passes a NULLstrwithlen == 0intomemcpy()invalue_init_string_(), which is undefined behavior and gets flagged by UBSan under glibc (thememcpyprototype there is markednonnull).The tokenizer delivers the empty key as
data == NULL, size == 0, so I guard the copy withif(len > 0)beforememcpy. The trailing NUL is still written, so short-string and long-string layouts are unaffected. Added a regression test (bug-issue13) that parses{"":1}and checks the empty key maps to the expected value.Fixes #13.