Service crash via disputed extract_name heap overwrite
Published Dec 31, 2021 · Updated Aug 4, 2024
A disputed heap buffer overflow in dnsmasq 2.86 allows remote attackers to crash the service through crafted DNS data. The OSS-Fuzz harness passes extract_name an undersized heap buffer through hash_questions, and the function writes one byte beyond the allocation. The upstream maintainer states that incomplete fuzzer initialization creates the condition and that the affected code receives an adequate buffer in real deployments.
Summary
What happened
A disputed heap buffer overflow in dnsmasq 2.86 allows remote attackers to crash the service through crafted DNS data. The OSS-Fuzz harness passes extract_name an undersized heap buffer through hash_questions, and the function writes one byte beyond the allocation. The upstream maintainer states that incomplete fuzzer initialization creates the condition and that the affected code receives an adequate buffer in real deployments.
The record
- CVE
- CVE-2021-45953
- Published
- Dec 31, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787
- Attack vector
- network
- Privileges
- unauthenticated
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.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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