CVE-2023-28452
An issue was discovered in CoreDNS through 1.10.1. There is a vulnerability in DNS resolving software, which triggers a resolver to ignore valid responses, thus causing denial of service for normal...
CVE-2023-28452 affects Go github.com/coredns/coredns (CVSS 7.5, High).
No known exploitation. EPSS puts it in the 50th percentile. Fixed in 1.11.0.
No public exploit knownFix1.11.0Upgrade to this build
e.g. OID 1.3.6.1.4.1.25623.1.1.16.2026.4018
What to do
Find your product and version, then upgrade to the build on the right.
- Go github.com/coredns/corednsAffected: < 1.11.0Upgrade to: 1.11.0Stated by: GitHub advisory
- Coredns.io CorednsAffected: ≤ 1.10.1Upgrade to: after 1.10.1Stated by: NVD
Versions as the sources state them. Full version matrix after sign-in
What it is
From the CVE record
CoreDNS vulnerable to TuDoor Attacks
In plain language
No plain-language summary for this CVE yet.
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
- CISA KEV
Not in the catalog. CISA has not confirmed exploitation.
- Public exploits
No public exploit or proof of concept found in the sources we track.
- EPSS
0.6% chance of exploitation activity in the next 30 days, which ranks it in the 50th percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
Lifecycle
6 events over 645 days, from the signal feeds we watch.
- OpenVAS check added
- Patch availablerecord updated
- Publishedweakness classified, att&ck mapped
Affected products
And 1 more affected product. See all after sign-in
Technical detail
CVSS 3.1 vector
Open in the CVSS calculatorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Scored 7.5 by NVD.
How it is reached
- Attack Vector NetworkExploitable remotely over the network without any special conditions
- Attack Complexity LowNo special conditions — the attack can be reliably reproduced
- Privileges Required NoneNo authentication required — anyone can exploit this
- User Interaction NoneNo user interaction needed — fully automated exploitation
Scope
- Scope UnchangedImpact is limited to the vulnerable component itself
Impact if exploited
- Confidentiality NoneNo confidentiality impact
- Integrity NoneNo integrity impact
- Availability HighTotal denial of service — the component is completely unavailable
Weaknesses
ATT&CK techniques
Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.
- Initial AccessT1078Valid Accountsmedium confidence
Sources
References in the record
- nvd.nist.gov/vuln/detail/CVE-2023-28452
- github.com/coredns/coredns/commit/604a902e2c7e0317aecaa3666124079c75a31573
- coredns.io
And 4 more references. See all after sign-in
Questions about CVE-2023-28452
- Is CVE-2023-28452 being exploited?
- No exploitation is confirmed and no public exploit is known. EPSS puts the chance of exploitation in the next 30 days at 0.6%.
- Which versions are affected by CVE-2023-28452?
- Github.com/coredns/coredns: < 1.11.0. CoreDNS: ≤ 1.10.1.
- How do I fix or mitigate CVE-2023-28452?
- Upgrade to 1.11.0 or later. The advisory is on github.com.
Last updated
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for Go, not every advisory.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI