Quick answers
- Is CVE-2023-30464 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2023-30464 being exploited in the wild.
- How severe is CVE-2023-30464?
- Low severity, with a CVSS score of 3.7, published 18 September 2024.
- Which products and versions are affected?
- CoreDNS <= 1.10.1; github.com/coredns/coredns (Go) <= 1.10.1, SEMVER:introduced=0,fixed=1.11.0, SEMVER:introduced=0,last_affected=1.10.1.
- Is there a fix for CVE-2023-30464?
- Yes. github.com/coredns/coredns (Go): upgrade to 1.11.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2023-30464 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2023-30464?
- Check whether you run CoreDNS or github.com/coredns/coredns (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- github.com/coredns/coredns (Go): upgrade to 1.11.0 or later
go get github.com/coredns/coredns@v1.11.0
Technical details
CoreDNS through version 1.10.1 is susceptible to DNS cache poisoning via a birthday attack (CWE-290). The vulnerability allows a remote, unauthenticated attacker to inject forged DNS records into the cache by sending a high volume of malicious responses that match the transaction ID and port of a legitimate pending query. Successful exploitation requires the attacker to overcome high complexity due to the probabilistic nature of the birthday attack. A fix has been identified in the project's source code repository, though specific patched release versions should be verified against the latest project updates.
Affected products
- CoreDNS CoreDNS <= 1.10.1
Identifiers
- CVE-2023-30464
- GHSA-h92q-fgpp-qhrq
- GO-2024-3134
Timeline
- 2024-09-18: advisory: GitHub Advisory published
- 2024-09-18: disclosed: NVD publication date