VulnerabilityPublished 3 Apr 2024Updated 21 Nov 2025

CVE-2024-31419: Exposure of Sensitive System Information to an Unauthorized Control Sphere

Source CVE Database V5

Not known to be exploited · CVSS 4.3 Medium.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

4.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 33% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 3 Apr 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

To mitigate CVE-2024-31419, organizations should take the following specific actions: 1) Immediately audit OpenShift Virtualization deployments to identify if the DownwardMetrics feature is enabled by default. 2) Disable the DownwardMetrics feature if it is not essential for operational monitoring, especially in multi-tenant or sensitive environments. 3) If metrics exposure is required, restrict access to trusted namespaces and guests through strict RBAC policies and network segmentation to limit unauthorized access. 4) Monitor virtual machine guest activities for unusual access patterns to host metrics. 5) Stay updated with Red Hat and OpenShift vendor advisories for patches or official mitigations and apply them promptly once available. 6) Consider implementing additional host-level monitoring and anomaly detection to identify potential reconnaissance or lateral movement attempts. 7) Educate administrators on the risks of default-enabled features that expose host information and enforce secure configuration baselines. These targeted steps go beyond generic advice by focusing on configuration auditing, access control tightening, and proactive monitoring tailored to this specific vulnerability.

Description

An information disclosure flaw was found in OpenShift Virtualization. The DownwardMetrics feature was introduced to expose host metrics to virtual machine guests and is enabled by default. This issue could expose limited host metrics of a node to any guest in any namespace without being explicitly enabled by an administrator.

Impact

The primary impact of CVE-2024-31419 is the unauthorized disclosure of limited host system metrics to virtual machine guests in OpenShift Virtualization environments. While the information disclosed is limited, it can provide attackers with valuable reconnaissance data about the host node, such as resource usage, performance characteristics, or other operational metrics. This information can be leveraged to identify potential weaknesses, optimize attack timing, or facilitate lateral movement within the cluster. For organizations running multi-tenant OpenShift clusters or sensitive workloads, this could increase the risk of targeted attacks or data breaches. However, since the vulnerability does not affect integrity or availability, the direct damage is limited to confidentiality exposure. The requirement for some privilege level reduces the attack surface but does not eliminate risk, especially in environments where guest VMs may be compromised or malicious. Overall, the vulnerability could aid attackers in escalating their access or planning more sophisticated attacks, impacting cloud service providers, enterprises, and government agencies relying on OpenShift Virtualization.

References

Community reviews

Loading reviews…