Fix: Buffer overflow in CHDDisc::tryOpen#2384
Open
LucaPalumbo wants to merge 1 commit into
Open
Conversation
Owner
|
|
Author
|
I opened an issue on libchdr. |
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
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.
I have identified a potential stack buffer overflow vulnerability in the
CHDDisk::TryOpenfunction. The issue occurs when the function parses the header of a CHD file usingsscanfwith an unbounded%sformatter.Because the destination buffers for the parsed strings (such as type, subtype, pgtype, and pgsub) are only 16 bytes in length, parsing a malformed or maliciously crafted CHD header can overflow these buffers. The theoretical maximum write is bounded only by the size of the temp buffer, which is 512 bytes (not enough to reach the return address in stack).
The bug is present in every of the following lines:
since the format strings are defined as:
A possible fix would be to use %15s everywhere, like in this PR.
Next step:
I think the same fix should be applied also to the dependency https://github.com/flyinghead/libchdr to always avoid the occurrence of the bug.