Bound RZIP chunk allocations - #2415
Open
acts-1631 wants to merge 3 commits into
Open
Conversation
CUE and GDI descriptor parsing continued appending after a quoted filename reached end of input. A malformed descriptor could consume CPU and memory until Flycast stopped responding. Treat failed character extraction as an invalid descriptor while skipping whitespace and while scanning quoted filenames.
The ISO9660 reader constructed filenames using record lengths supplied by the disc without confirming that the record remained in the loaded directory buffer. A malformed image could read past that buffer. Reject incomplete records and filenames before accessing their fields.
RZIP savestate headers controlled allocation sizes without a limit or an allocation failure boundary. A malicious savestate could terminate Flycast by requesting an impractically large allocation. Reject oversized chunks and handle allocation failures when reading compressed chunk data.
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.
Flycast used maxChunkSize and compressed chunk sizes from an RZIP
savestate as allocation sizes without limits. A malformed savestate
could trigger an impractically large allocation and terminate Flycast.
This rejects zero or oversized chunk values, caps compressed chunks to
the corresponding valid zlib bound, and handles allocation failure as a
load error.