# CVE-2013-4786: Information disclosure in n/a

> Remote attackers can extract password hashes from IPMI RAKP messages to conduct offline guessing attacks, compromising BMC authentication.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **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:** 9 Oct 2026
- **Also known as:** GHSA-5qfx-g363-pvpg

## What is CVE-2013-4786?

CVE-2013-4786 is a high-severity 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 IPMI 2.0 specification supports RMCP+ Authenticated Key-Exchange Protocol (RAKP) authentication, which allows remote attackers to obtain password hashes and conduct offline password guessing attacks by obtaining the HMAC from a RAKP message 2 response from a BMC.

Weakness: CWE-255

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

It affects 2 products.


Products: Intel Intelligent Platform Management Interface, Oracle Fujitsu M10 Firmware.

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

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

## Is CVE-2013-4786 being exploited?

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

Public exploit code:

- CVE-2013-4786 Go exploitation tool (github_poc): https://github.com/fin3ss3g0d/CosmicRakp
- IPMI 2.0 RAKP Remote SHA1 Password Hash Retrieval (metasploit)
- Intelligent Platform Management Interface - Information Disclosure (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2013-4786 is a high-severity 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-4786 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-4786/ (Markdown: https://insights.sbomify.com/CVE-2013-4786/index.md)
```

## Sources

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

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