Validate PGF parser bounds - #21966
Open
acts-1631 wants to merge 1 commit into
Open
Conversation
Track remaining input while parsing PGF headers and tables, and validate all glyph bitstream reads. This rejects truncated user fonts before they can access memory outside the supplied buffer.
Collaborator
|
|
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
3 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.
PGF parsing validated only the base header before reading revision-specific data and table-driven bitstreams. A truncated revision-3 font supplied by PSP content could read past the font buffer and crash PPSSPP.
Track remaining input while parsing headers and tables, and validate glyph bitstream reads before dereferencing them.