Coredns: cd bit response is cached and served later
A flaw was found in coredns. This issue could lead to invalid cache entries returning due to incorrectly implemented caching.
- Published
- Apr 25, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.8% · 54th percentile
- CWE
- CWE-524
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
21
Monitor
Low priority for now.
- CVSS
- 21 / 40 · 5.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.8%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · redhat
- 5.3
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpAffected systems
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.
github.com/coredns/coredns coredns
- before 1.11.2affected · semver
Red Hat Logging Subsystem for Red Hat OpenShift
- all versionsunknown
Red Hat Red Hat Advanced Cluster Management for Kubernetes 2
- all versionsaffected
Red Hat Red Hat OpenShift Container Platform 4.13
- v4.13.0-202408260940.p0.ge70f097.assembly.stream.el8 and laternot affected · rpm
Red Hat Red Hat OpenShift Container Platform 4.14
- v4.14.0-202408260910.p0.gfdd6037.assembly.stream.el8 and laternot affected · rpm
Red Hat Red Hat OpenShift Container Platform 4.15
- v4.15.0-202407230407.p0.g1326282.assembly.stream.el9 and laternot affected · rpm
Red Hat Red Hat OpenShift Container Platform 4.16
- v4.16.0-202406131906.p0.g04d84f7.assembly.stream.el9 and laternot affected · rpm
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Go | github.com/coredns/coredns | before 1.11.2 | 1.11.2 |
| SUSE:Package Hub 15 SP6 | coredns | before 1.11.3-bp156.4.3.1 | 1.11.3-bp156.4.3.1 |
| SUSE:Package Hub 15 SP6 | coredns | before 1.11.3-bp156.4.3.1 | 1.11.3-bp156.4.3.1 |
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| github.com/coredns/coredns coredns | 1.11.2 | Vendor (CNA) |
| Go:github.com/coredns/coredns | 1.11.2 | Package registry (OSV) |
| opensuse:coredns | 1.11.3-bp156.4.3.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| suse:coredns | 1.11.3-bp156.4.3.1 · SUSE:Package Hub 15 SP6 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- low · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- Low
- Availability impact
- None
Weakness class (CWE)
CWE-524 · Use of Cache Containing Sensitive InformationCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- access.redhat.com/errata/RHSA-2024:0041
- access.redhat.com/errata/RHSA-2024:4850
- access.redhat.com/errata/RHSA-2024:6009
- access.redhat.com/errata/RHSA-2024:6406
- access.redhat.com/security/cve/CVE-2024-0874
- bugzilla.redhat.com/show_bug.cgi?id=2219234
- github.com/coredns/coredns/issues/6186
- github.com/coredns/coredns/pull/6354
Vendor advisories and official records. Exploit/PoC links are deliberately left out.