# CVE-2024-0874: Coredns: cd bit response is cached and served later

> Attackers can retrieve invalid cached DNS entries due to flawed caching logic in CoreDNS, potentially exposing stale or incorrect data.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Apr 2024
- **Updated:** 13 Oct 2026
- **Also known as:** AZL-40201, AZL-40222, CLEANSTART-2026-GW29124, ECHO-deff-f49a-144e, GHSA-m9w6-wp3h-vq8g, GO-2024-2785, openSUSE-SU-2024:13620-1

## What is CVE-2024-0874?

CVE-2024-0874 is a medium-severity vulnerability in Logging Subsystem for Red Hat OpenShift, published on 25 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A flaw was found in coredns. This issue could lead to invalid cache entries returning due to incorrectly implemented caching.

Weakness: CWE-524 (Use of Cache Containing Sensitive Information)

## Which versions are affected by CVE-2024-0874?

3 open source packages ship an affected version, including github.com/coredns/coredns.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/coredns/coredns` | Go | All versions | 1.11.2 |
| `github.com/coredns/coredns` | Go | All versions | 1.11.2 |
| `github.com/coredns/coredns` | Go | All versions | 1.11.2 |

## How do I fix CVE-2024-0874?

Upgrade github.com/coredns/coredns to 1.11.2 or later.

## Is CVE-2024-0874 being exploited?

There is no known exploitation of CVE-2024-0874 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-0874 and fix it if it is affected.

What it is: CVE-2024-0874 is a medium-severity vulnerability in Logging Subsystem for Red Hat OpenShift, published on 25 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-0874 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/coredns/coredns (Go): affected all versions; fixed in 1.11.2
- github.com/coredns/coredns (Go): affected all versions; fixed in 1.11.2
- github.com/coredns/coredns (Go): affected all versions; fixed in 1.11.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-0874/ (Markdown: https://insights.sbomify.com/CVE-2024-0874/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-0874
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-0874
- OSV: https://osv.dev/vulnerability/CVE-2024-0874

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-0874/
Summaries are generated and may contain mistakes; the official description above is the record.