DNSSEC bypass via unvalidated NXDOMAIN answer records
Published May 19, 2020 · Updated Aug 4, 2024
DNSSEC validation bypass in PowerDNS Recursor 4.1.0 through 4.3.0 allows man-in-the-middle attackers to spoof denial of existence. SyncRes::processAnswer accepts answer-section records from an NXDOMAIN response lacking an SOA without properly validating their DNSSEC signatures. The attacker must control the DNS response path and can make an existing name appear nonexistent, without reported system compromise.
Summary
What happened
DNSSEC validation bypass in PowerDNS Recursor 4.1.0 through 4.3.0 allows man-in-the-middle attackers to spoof denial of existence. SyncRes::processAnswer accepts answer-section records from an NXDOMAIN response lacking an SOA without properly validating their DNSSEC signatures. The attacker must control the DNS response path and can make an existing name appear nonexistent, without reported system compromise.
The record
- CVE
- CVE-2020-12244
- Published
- May 19, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-347, T1557
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 19, 2020CVE 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