# CVE-2022-3409: Unauthenticated out of bounds stack write in bmcweb

> An attacker can cause denial of service in OpenBMC's bmcweb by sending malformed multipart HTTP headers that trigger a heap buffer overflow.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Oct 2022
- **Updated:** 5 May 2025
- **Also known as:** GHSA-42qg-gfqm-p7q6

## What is CVE-2022-3409?

CVE-2022-3409 is a high-severity memory corruption vulnerability in OpenBMC, published on 27 Oct 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability in bmcweb of OpenBMC Project allows user to cause denial of service. This vulnerability was identified during mitigation for CVE-2022-2809. When fuzzing the multipart_parser code using AFL++ with address sanitizer enabled to find smallest memory corruptions possible. It detected problem in how multipart_parser handles unclosed http headers. If long enough http header is passed in the multipart form without colon there is one byte overwrite on heap. It can be conducted multiple times in a loop to cause DoS.

Weakness: CWE-787 (Out-of-bounds Write), CWE-229 (Improper Handling of Values), CWE-121 (Stack-based Buffer Overflow)

## Which versions are affected by CVE-2022-3409?

It affects 1 product.


Products: Openbmc-Project Openbmc.

## How do I fix CVE-2022-3409?

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

## Is CVE-2022-3409 being exploited?

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

## Other vulnerabilities in OpenBMC

- [CVE-2021-39296](https://insights.sbomify.com/CVE-2021-39296/): Auth bypass in n/a (critical 10.0)
- [CVE-2020-14156](https://insights.sbomify.com/CVE-2020-14156/): Misconfiguration in n/a (high 8.8)
- [CVE-2022-2809](https://insights.sbomify.com/CVE-2022-2809/): Unauthenticated out of bounds heap write in bmcweb (high 8.2)
- [CVE-2021-39295](https://insights.sbomify.com/CVE-2021-39295/): Denial of service in n/a (high 7.5)
- [CVE-2022-35729](https://insights.sbomify.com/CVE-2022-35729/): Denial of service in OpenBMC (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-3409 and fix it if it is affected.

What it is: CVE-2022-3409 is a high-severity memory corruption vulnerability in OpenBMC, published on 27 Oct 2022. 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-2022-3409 in the wild and no public exploit code.

Affected product: OpenBMC. 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-2022-3409/ (Markdown: https://insights.sbomify.com/CVE-2022-3409/index.md)
```

## Sources

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

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