Fix buffer overrun in get_bool()
#133
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
A truncated buffer could lead to an out of bounds memory access. Instead of checking the buffer before we are accessing the first byte beyond the end of the before, we first read it and _then_ checked it. This change reverses the actions so that no out-of-bounds read occurs. We have not found this bug in our previous fuzzing because of the way we read the test data: std::string always adds a trailing 0 byte so that it can be trivially converted to a C string. Technically, this trailing 0 byte is part of the buffer, but is not returned as part of the buffer length. Therefore, accessing a single byte beyond the end of the buffer did not trigger the address sanitizer.
olegfedorovdev
approved these changes
Jul 15, 2025
joto
approved these changes
Jul 15, 2025
artemp
added a commit
to mapnik/mapnik
that referenced
this pull request
Jul 17, 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.
A truncated buffer could lead to an out of bounds memory access when calling
get_bool(). Instead of checking the buffer before we are accessing the first byte beyond the end of the before, we first read it and then checked it. This change reverses the actions so that no out-of-bounds read occurs.We have not found this bug in our previous fuzzing because of the way we read the test data:
std::stringalways adds a trailing NUL byte so that it can be trivially converted to a C string. Technically, this trailing NUL byte is part of the buffer, but is not returned as part of the buffer length. Therefore, accessing a single byte beyond the end of the buffer did not trigger the address sanitizer.