# CVE-2024-36435: Memory corruption in n/a

> Unauthenticated attackers can trigger a stack buffer overflow in Supermicro BMC firmware to achieve arbitrary remote code execution.

- **Severity:** Critical 9.8 (`CVSS:3.1/AC:L/AV:N/A:H/C:H/I:H/PR:N/S:U/UI:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Jul 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-v8px-cfvm-hpmm

## What is CVE-2024-36435?

CVE-2024-36435 is a critical memory corruption vulnerability in n/a, published on 11 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered on Supermicro BMC firmware in select X11, X12, H12, B12, X13, H13, and B13 motherboards (and CMM6 modules). An unauthenticated user can post crafted data to the interface that triggers a stack buffer overflow, and may lead to arbitrary remote code execution on a BMC.

Weakness: CWE-121 (Stack-based Buffer Overflow)

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


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

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

## Is CVE-2024-36435 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-36435 is a critical memory corruption vulnerability in n/a, published on 11 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-36435 in the wild and no public exploit code.

Affected product: n/a. 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-36435/ (Markdown: https://insights.sbomify.com/CVE-2024-36435/index.md)
```

## Sources

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

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