Fix out of bounds reads in packet parsing#2954
Closed
domenpk wants to merge 3 commits intonmap:masterfrom
Closed
Conversation
Consuming bytes reduces the number of bytes left. Fix this for PAD1 case where it was increased instead.
PacketParser::parse_packet code does not account for an edge case where a RAW packet is added at the end of this_packet[], causing an out of bounds read in the array processing code that follows.
|
Thanks for these fixes! The The |
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
3 participants
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.
Should be straightforward. I do not think these have any security impact, but reading out of bounds isn't nice.
This was found with AFL and the test code included in last commit.
Btw, while doing this, I have also come across another out of bounds read in DNS code, which is already described in https://tomerfry.github.io/2023/05/26/Fuzzing-NMAP-With-AFL++.html
From my experiments it's an over-read in input buffer to DNS::Packet::parseFromBuffer(). I haven't analysed it enough to figure out the root cause, hence no patch.