Disputed heap overwrite from undersized fuzz buffer
Published Dec 31, 2021 · Updated Aug 4, 2024
A heap-buffer overwrite reported in dnsmasq 2.86's answer_request occurs only under an OSS-Fuzz harness with an undersized buffer. The harness allocated 76 bytes for daemon->namebuff, while production initialization allocates MAXDNAME or twice MAXDNAME and the crash disappeared when the harness matched that size. The maintainer disputes this as a product vulnerability, so no attacker-reachable impact in dnsmasq has been demonstrated.
Summary
What happened
A heap-buffer overwrite reported in dnsmasq 2.86's answer_request occurs only under an OSS-Fuzz harness with an undersized buffer. The harness allocated 76 bytes for daemon->namebuff, while production initialization allocates MAXDNAME or twice MAXDNAME and the crash disappeared when the harness matched that size. The maintainer disputes this as a product vulnerability, so no attacker-reachable impact in dnsmasq has been demonstrated.
The record
- CVE
- CVE-2021-45957
- Published
- Dec 31, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Dec 31, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo