# CVE-2013-4782: Auth bypass in n/a

> Remote attackers can bypass authentication and execute arbitrary IPMI commands on Supermicro BMCs using cipher suite zero.

- **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 Jul 2013
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-m5ff-xqmw-4569

## What is CVE-2013-4782?

CVE-2013-4782 is a critical authentication bypass vulnerability in n/a, published on 8 Jul 2013. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Supermicro BMC implementation allows remote attackers to bypass authentication and execute arbitrary IPMI commands by using cipher suite 0 (aka cipher zero) and an arbitrary password.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Supermicro Bmc.

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

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

## Is CVE-2013-4782 being exploited?

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

Public exploit code:

- IPMI 2.0 Cipher Zero Authentication Bypass Scanner (metasploit)

## Fix prompt for AI coding agents

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

What it is: CVE-2013-4782 is a critical authentication bypass vulnerability in n/a, published on 8 Jul 2013. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2013-4782 exists.

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-4782/ (Markdown: https://insights.sbomify.com/CVE-2013-4782/index.md)
```

## Sources

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

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