# CVE-2024-33394: kubevirt allows a local attacker to execute arbitrary code via a crafted command

> A local attacker can execute arbitrary code in KubeVirt by sending a crafted command to retrieve the token component.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 2 May 2024
- **Updated:** 2 Aug 2024
- **Also known as:** AZL-64787, AZL-64791, GHSA-4q63-mr2m-57hf, GO-2024-2816, MINI-2g58-mm6j-mr7r, MINI-m52v-36g6-m7j9, SUSE-SU-2024:2246-1, SUSE-SU-2024:2318-1, openSUSE-SU-2024:14058-1

## What is CVE-2024-33394?

CVE-2024-33394 is a medium-severity code injection vulnerability in n/a, published on 2 May 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue in kubevirt kubevirt v1.2.0 and before allows a local attacker to execute arbitrary code via a crafted command to get the token component.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

3 open source packages ship an affected version, including kubevirt.io/kubevirt. It affects 1 product.


| 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 |
| `kubevirt` | SUSE:Linux Enterprise Micro 5.5 | All versions | 1.1.1-150500.8.18.1 |
| `kubevirt` | SUSE:Linux Enterprise Module for Containers 15 SP5 | All versions | 1.1.1-150500.8.18.1 |
| `kubevirt` | SUSE:Linux Enterprise Module for Containers 15 SP6 | All versions | 1.1.1-150600.5.3.2 |
| `kubevirt` | openSUSE:Leap 15.5 | All versions | 1.1.1-150500.8.18.1 |
| `kubevirt` | openSUSE:Leap 15.6 | All versions | 1.1.1-150600.5.3.2 |
| `kubevirt` | openSUSE:Tumbleweed | All versions | 1.2.2-2.1 |

Products: Kubevirt Kubevirt.

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

Upgrade to a fixed version.

## Is CVE-2024-33394 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-14316](https://insights.sbomify.com/CVE-2020-14316/): Privilege Escalation in kubevirt (critical 9.9)
- [CVE-2022-1798](https://insights.sbomify.com/CVE-2022-1798/): Path Traversal vulnerability in Kubevirt (high 8.7)
- [CVE-2025-64324](https://insights.sbomify.com/CVE-2025-64324/): KubeVirt Vulnerable to Arbitrary Host File Read and Write (high 8.5)
- [CVE-2023-26484](https://insights.sbomify.com/CVE-2023-26484/): On a compromised KubeVirt node, the virt-handler service account can be used to modify all node specs (high 8.2)
- [CVE-2026-13201](https://insights.sbomify.com/CVE-2026-13201/): Path traversal in Red Hat Container Native Virtualization 4.12 (high 7.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-33394 is a medium-severity code injection vulnerability in n/a, published on 2 May 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-33394 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-33394/ (Markdown: https://insights.sbomify.com/CVE-2024-33394/index.md)
```

## Sources

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

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