LiveActive security incident?Get immediate response
CVE Record

CVE-2024-0874: 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.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CoreDNS can incorrectly cache a DNS response tied to the CD bit and later serve an invalid cached answer. For organizations using affected OpenShift or Red Hat ACM components, this is mainly a DNS trust and correctness issue, not a data theft or outage scenario in the supplied sources.

Executive priority

Prioritize during normal security maintenance, sooner for environments where DNS correctness directly affects routing, service discovery, or security controls. There is no supplied evidence of active exploitation or severe business disruption.

Technical view

The flaw is an incorrectly implemented caching behavior in CoreDNS. CVSS 3.1 is 5.3 with network attack vector, no privileges, no user interaction, unchanged scope, no confidentiality or availability impact, and low integrity impact. Red Hat lists several OpenShift CoreDNS packages and ACM lighthouse-agent as affected.

Likely exposure

Confirmed exposure is in listed Red Hat OpenShift Container Platform 4.13 through 4.16 CoreDNS packages and Red Hat ACM lighthouse-agent. The bundle does not prove all upstream CoreDNS versions or non-Red Hat distributions are affected. Red Hat lists the OpenShift Logging Loki package as unaffected.

Exploitation context

The provided bundle marks KEV as false and contains no cited evidence of active exploitation. The CVSS vector indicates remote reachability without authentication, but the documented impact is limited to integrity of cached DNS responses.

Researcher notes

Focus analysis on CoreDNS cache handling of CD-bit responses and downstream package backports. Public issue and pull request references exist, but the bundle does not include a complete upstream affected-version range or detailed fixed-version mapping for every deployment.

Mitigation direction

  • Apply relevant Red Hat errata for affected OpenShift and ACM components.
  • Update affected CoreDNS-related container images through supported vendor channels.
  • For non-Red Hat CoreDNS deployments, check upstream CoreDNS and vendor guidance.
  • Treat DNS cache behavior changes as operationally sensitive and test before production rollout.

Validation and detection

  • Inventory OpenShift and ACM versions against the affected product list.
  • Confirm deployed CoreDNS package names match affected Red Hat package entries.
  • Review vendor advisories to identify the fixed release applicable to each platform.
  • Verify the OpenShift Logging Loki package is not incorrectly flagged as affected.
Prepared
Confidence
medium
Sources
10

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-524: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Container behavior lookup

The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2024-0874 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
5Timeline events
2ADP providers
9Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: partial

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N3.91.4redhat

Vulnerability scoring details

Base CVSS 3.1 score

5.3Medium
CVSS 3.1 vector shape for CVE-2024-0874Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. Source timelineredhat

    Reported to Red Hat.

  2. Source timelineredhat

    Made public.

  3. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  4. CVE publishedCVE Program

    The CVE record was published.

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Unknown vendorcorednscoredns, 0unaffected
Red HatRed Hat OpenShift Container Platform 4.13openshift4/ose-coredns, v4.13.0-202408260940.p0.ge70f097.assembly.stream.el8affected
Red HatRed Hat OpenShift Container Platform 4.14openshift4/ose-coredns, v4.14.0-202408260910.p0.gfdd6037.assembly.stream.el8affected
Red HatRed Hat OpenShift Container Platform 4.15openshift4/ose-coredns-rhel9, v4.15.0-202407230407.p0.g1326282.assembly.stream.el9affected
Red HatRed Hat OpenShift Container Platform 4.16openshift4/ose-coredns-rhel9, v4.16.0-202406131906.p0.g04d84f7.assembly.stream.el9affected
Red HatLogging Subsystem for Red Hat OpenShiftopenshift-logging/logging-loki-rhel9unaffected
Red HatRed Hat Advanced Cluster Management for Kubernetes 2rhacm2/lighthouse-agent-rhel9affected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-524 · source CWE mapping

Use of Cache Containing Sensitive Information

Use of Cache Containing Sensitive Information represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.