CVE-2023-30464
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCoreDNS through 1.10.1 enables attackers to achieve DNS cache poisoning and inject fake responses via a birthday attack.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceCoreDNS through 1.10.1 contains a vulnerability that allows attackers to perform DNS cache poisoning by exploiting the birthday attack phenomenon. This occurs due to insufficient entropy or predictability in the DNS query transaction IDs, enabling an attacker to inject malicious DNS responses into the cache by sending multiple crafted DNS queries and matching the transaction ID within the limited ID space.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 1.10.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check CoreDNS versionRun 'coredns -version' or check the version of the coredns binary in use (for example: docker images, kubernetes pod, or systemctl status coredns)Affected if The installed version is 1.10.1 or any earlier version (for example: 1.10.0, 1.9.x, 1.8.x)
-
Verify CoreDNS is handling DNS queriesConfirm CoreDNS is configured as a DNS server (listening on port 53 UDP/TCP) and processing DNS queries - this is the default behavior when CoreDNS runs without specific proxy-only configurationsAffected if CoreDNS is serving DNS responses to clients (the vulnerability exists in the transaction ID generation for all DNS queries by default)
-
Confirm transaction ID entropy (optional deeper check)Inspect DNS query traffic from CoreDNS using a packet capture (for example: tcpdump -i any -n port 53) and observe the transaction ID patterns across multiple queriesAffected if Transaction IDs appear predictable, sequential, or show limited randomization (the vulnerability manifests as low entropy in the 16-bit transaction ID space)
A user is affected if their CoreDNS version is 1.10.1 or earlier and the server is handling DNS queries, since the flawed transaction ID generation affects all DNS responses by default.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade CoreDNS to a version newer than 1.10.1 which includes proper entropy for transaction IDs. If immediate upgrading is not possible, consider implementing DNS response validation mechanisms or deploying DNSSEC.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-30464 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-30464 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data