# CVE-2024-31419: Cnv: information disclosure through the usage of vm-dump-metrics

> Attackers can access limited host metrics from any guest VM due to default-enabled DownwardMetrics feature in OpenShift Virtualization.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Apr 2024
- **Updated:** 21 Nov 2025
- **Also known as:** GHSA-xrr8-23jx-fjvc

## What is CVE-2024-31419?

CVE-2024-31419 is a medium-severity vulnerability in Red Hat OpenShift Virtualization 4, published on 3 Apr 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-497 (Exposure of Sensitive System Information to an Unauthorized Control Sphere)

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


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

No fix has been published for CVE-2024-31419 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-31419 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-31419 is a medium-severity vulnerability in Red Hat OpenShift Virtualization 4, published on 3 Apr 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-31419 in the wild and no public exploit code.

Affected product: Red Hat OpenShift Virtualization 4. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-31419/ (Markdown: https://insights.sbomify.com/CVE-2024-31419/index.md)
```

## Sources

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

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