bpo-35214: Fix OOB memory access in unicode escape parser#10506
Merged
gpshead merged 3 commits intopython:masterfrom Nov 13, 2018
Merged
bpo-35214: Fix OOB memory access in unicode escape parser#10506gpshead merged 3 commits intopython:masterfrom
gpshead merged 3 commits intopython:masterfrom
Conversation
Loading
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Discovered using clang's MemorySanitizer when it ran
test_fstring'stest_misformed_unicode_character_name.An f-string ending in
\Nwould access one byte beyond the end ofthe string while looking for a potential
}.https://bugs.python.org/issue35214