# CVE-2024-31420: Cnv: dos through repeatedly calling vm-dump-metrics until virt handler crashes

> An attacker with guest access can crash the virtualization handler by repeatedly calling vm-dump-metrics, causing denial of service.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **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:** 20 Nov 2025
- **Also known as:** GHSA-vjhf-6xfr-5p9g, GO-2024-2688, MINI-78qf-q7m4-q48f, MINI-mjvw-3jmr-g2q9

## What is CVE-2024-31420?

CVE-2024-31420 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

A NULL pointer dereference flaw was found in KubeVirt. This flaw allows an attacker who has access to a virtual machine guest on a node with DownwardMetrics enabled to cause a denial of service by issuing a high number of calls to vm-dump-metrics --virtio and then deleting the virtual machine.

Weakness: CWE-476 (NULL Pointer Dereference)

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

3 open source packages ship an affected version, including kubevirt.io/kubevirt.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `kubevirt.io/kubevirt` | Go | All versions | None |
| `kubevirt.io/kubevirt` | Go | All versions to 1.2.0 | None |
| `kubevirt.io/kubevirt` | Go | All versions to 1.2.0 | None |

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

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

## Is CVE-2024-31420 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-31420 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-31420 in the wild and no public exploit code.

Affected packages and fixed versions:
- kubevirt.io/kubevirt (Go): affected all versions; no fix listed
- kubevirt.io/kubevirt (Go): affected all versions up to 1.2.0; no fix listed
- kubevirt.io/kubevirt (Go): affected all versions up to 1.2.0; no fix listed

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

## Sources

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

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