Fix invalid memory write #261
Merged
Conversation
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
hyperrealm
approved these changes
May 4, 2025
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.
There is no bounds check after fuzz_data_path() calls to ensure that the memory pointer (path_data, config_data) actually lies within the buffer and doesn't overflow.
This leads to:
Heap buffer overflow (write past allocated memory bounds)
Undefined behavior or even arbitrary memory writes
in this PR resolves a memory corruption issue in config_read_fuzzer by adding strict bounds checking, ensuring proper null termination, and avoiding out-of-bounds access in config and path data handling.
issue Link: https://issues.oss-fuzz.com/issues/391659746