# CVE-2024-21935: Path traversal in AMD Instinct™ MI300X

> Privileged attackers can manipulate Redfish API commands to delete files from the root directory, causing data corruption on AMD Instinct MI300X accelerators.

- **Severity:** Medium 5.0 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:L/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:** 23 Sep 2025
- **Updated:** 24 Sep 2025
- **Also known as:** GHSA-pfx9-w6cc-q924

## What is CVE-2024-21935?

CVE-2024-21935 is a medium-severity path traversal vulnerability in AMD Instinct™  MI300X, published on 23 Sep 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Improper input validation in Satellite Management Controller (SMC) may allow an attacker with privileges to manipulate Redfish® API commands to remove files from the local root directory, potentially resulting in data corruption.

Weakness: CWE-241 (Improper Handling of Unexpected Data Type)

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


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

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

## Is CVE-2024-21935 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-21935 is a medium-severity path traversal vulnerability in AMD Instinct™  MI300X, published on 23 Sep 2025. 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-21935 in the wild and no public exploit code.

Affected product: AMD Instinct™  MI300X. 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-21935/ (Markdown: https://insights.sbomify.com/CVE-2024-21935/index.md)
```

## Sources

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

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