Cache poisoning via unaggregated concurrent DNS queries
Published Sep 18, 2024 · Updated Sep 19, 2024
DNS cache poisoning in CoreDNS 1.10.1 and earlier allows remote attackers to inject forged DNS responses via a birthday attack. CoreDNS permits multiple simultaneous upstream queries for the same name instead of aggregating them, increasing the chance that a forged reply matches a transaction ID. Exploitation requires network access for queries and spoofed replies; a successful collision stores attacker-controlled DNS data for subsequent clients.
Summary
What happened
DNS cache poisoning in CoreDNS 1.10.1 and earlier allows remote attackers to inject forged DNS responses via a birthday attack. CoreDNS permits multiple simultaneous upstream queries for the same name instead of aggregating them, increasing the chance that a forged reply matches a transaction ID. Exploitation requires network access for queries and spoofed replies; a successful collision stores attacker-controlled DNS data for subsequent clients.
The record
- CVE
- CVE-2023-30464
- Published
- Sep 18, 2024
- Updated
- Sep 19, 2024
- Vendor
- CoreDNS
- Product
- CoreDNS
- Classifications
- CWE-290, CAPEC-142, T1565.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 18, 2024CVE publishedPublication date reported by the CVE source.
- Sep 19, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=1.10.1
What conditions does exploitation require?
What is affected?
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