# CVE-2013-3607: Memory corruption in n/a

> Remote attackers can execute arbitrary code on Supermicro BMCs via stack-based buffer overflows in the IPMI web interface login fields.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Sep 2013
- **Updated:** 6 Aug 2024
- **Also known as:** CVE-2013-3621, GHSA-p6cp-w5h4-4h2m

## What is CVE-2013-3607?

CVE-2013-3607 is a critical memory corruption vulnerability in n/a, published on 8 Sep 2013. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multiple stack-based buffer overflows in the web interface in the Intelligent Platform Management Interface (IPMI) implementation on Supermicro H8DC*, H8DG*, H8SCM-F, H8SGL-F, H8SM*, X7SP*, X8DT*, X8SI*, X9DAX-*, X9DB*, X9DR*, X9QR*, X9SBAA-F, X9SC*, X9SPU-F, and X9SR* devices allow remote attackers to execute arbitrary code on the Baseboard Management Controller (BMC), as demonstrated by the (1) username or (2) password field in login.cgi.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2013-3607?

It affects 133 products.


Products: Supermicro H8dcl-6f, Supermicro H8dcl-If, Supermicro H8dct-Hibqf, Supermicro H8dct-Hln4f, Supermicro H8dct-Ibqf, Supermicro H8dg6-F, Supermicro H8dgg-Qf, Supermicro H8dgi-F, Supermicro H8dgt-Hf, Supermicro H8dgt-Hibqf, Supermicro H8dgt-Hlf, Supermicro H8dgt-Hlibqf, Supermicro H8dgu-F, Supermicro H8dgu-Ln4f\+, Supermicro H8scm-F, Supermicro H8sgl-F, Supermicro H8sme-F, Supermicro H8sml-7, Supermicro H8sml-7f, Supermicro H8sml-I and 113 more.

## How do I fix CVE-2013-3607?

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

## Is CVE-2013-3607 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2013-3608](https://insights.sbomify.com/CVE-2013-3608/): Command injection in n/a (critical 10.0)
- [CVE-2013-3609](https://insights.sbomify.com/CVE-2013-3609/): Missing authorization in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-3607 and fix it if it is affected.

What it is: CVE-2013-3607 is a critical memory corruption vulnerability in n/a, published on 8 Sep 2013. 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-2013-3607 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-2013-3607/ (Markdown: https://insights.sbomify.com/CVE-2013-3607/index.md)
```

## Sources

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

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