# CVE-2024-33396: karmada vulnerable to arbitrary code execution via a crafted command

> A local attacker could potentially execute arbitrary code via crafted commands, though maintainers dispute this as intended behavior.

- **Severity:** High 8.4 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 May 2024
- **Updated:** 12 Oct 2026
- **Also known as:** GHSA-wccg-v638-j9q2, GO-2024-2817

## What is CVE-2024-33396?

CVE-2024-33396 is a high-severity 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 karmada-io karmada v1.9.0 and before allows a local attacker to execute arbitrary code via a crafted command to get the token component. NOTE: Then maintainer states that the behavior is intended design and notes that the researcher advisory does not provide evidence of arbitrary code execution.

Weakness: CWE-284 (Improper Access Control)

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

3 open source packages ship an affected version, including github.com/karmada-io/karmada.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/karmada-io/karmada` | Go | All versions | None |
| `github.com/karmada-io/karmada` | Go | All versions to 1.9.0 | None |
| `github.com/karmada-io/karmada` | Go | All versions to 1.9.0 | None |

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

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

## Is CVE-2024-33396 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-33396 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2024-33396 is a high-severity 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-33396 exists.

Affected packages and fixed versions:
- github.com/karmada-io/karmada (Go): affected all versions; no fix listed
- github.com/karmada-io/karmada (Go): affected all versions up to 1.9.0; no fix listed
- github.com/karmada-io/karmada (Go): affected all versions up to 1.9.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-33396/ (Markdown: https://insights.sbomify.com/CVE-2024-33396/index.md)
```

## Sources

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

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