Check length of buffer #106
Merged
Conversation
This file contains 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
Test plan: Added test that triggers stack-buffer-overflow in AddressSanitizer.
Co-authored-by: Jessica Winer <jwiner10@bloomberg.net>
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.
Describe your changes
Check the buffer length before reading bytes off the buffer.
Testing performed
I added a unit test that exposes the overflow. It fails in an ASAN build without the fix, and succeeds with the fix.
Additional context
This doesn't cause an ASAN failure when sending the bytes to the running server, since the memory region allocated to hold the wire bytes is much larger than what is actually sent by the client. The bytes read though are uninitialized regardless.