Skip to content

bpo-35214: Fix OOB memory access in unicode escape parser #10506

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
gpshead merged 3 commits into from
Nov 13, 2018
Merged

bpo-35214: Fix OOB memory access in unicode escape parser #10506

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
782568a
bpo-35214: Fix OOB memory access in f-string parser.
gpshead Nov 13, 2018
1af8580
Add a news entry.
gpshead Nov 13, 2018
db54123
Correct the news entry.
gpshead Nov 13, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Correct the news entry.
  • Loading branch information
@gpshead
gpshead committed Nov 13, 2018
commit db5412306854212d1dfe165e2a36a324bc78a604
5 changes: 3 additions & 2 deletions Misc/NEWS.d/next/Core and Builtins/2018-11-13-00-40-35.bpo-35214.OQBjph.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,2 +1,3 @@
Fixed an out of bounds memory access when parsing a malformed f-string
ending with ``\N``.
Fixed an out of bounds memory access when parsing a truncated unicode
escape sequence at the end of a string such as ``'\N'``. It would read
one byte beyond the end of the memory allocation.