Harden DNS response parser against malformed replies#14
Open
dfateyev wants to merge 1 commit into
Open
Conversation
The POSIX resolver parsed res_nquery() responses without validating record boundaries, trusting attacker-controlled header counts and RDLENGTH fields. A spoofed or malicious DNS reply could trigger out-of-bounds reads of the 64 KiB response buffer, causing crashes or leaking adjacent stack memory into the resolved addresses. - Bounds-check the fixed RR fields (TYPE/CLASS/TTL/RDLENGTH) and the question section before reading them. - Verify RDLENGTH stays within the response before use. - Guard the MX PREFERENCE subtraction against RDLENGTH < 2, which previously underflowed the unsigned length and advanced the cursor far past the buffer. - Require A/AAAA rdata to be large enough before inet_ntop() reads its fixed 4/16 bytes. - Advance the record cursor by the original RDLENGTH via a separate rdata pointer, decoupling it from the MX preference read. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
The POSIX resolver parsed
res_nquery()responses without validating record boundaries, trusting attacker-controlled header counts and RDLENGTH fields. A spoofed or malicious DNS reply could trigger out-of-bounds reads of the 64 KiB response buffer, causing crashes or leaking adjacent stack memory into the resolved addresses.inet_ntop()reads its fixed 4/16 bytes.