Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2013-4786: IPMI 2.0 RAKP Password Hash Disclosure

Published Jul 8, 2013 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.5High · v3
EPSS98.4%100th percentile
CISA KEVNoNot listed
In the wildReported6 exploitation records in Mallory
Vendors
Oracle CorporationIntel Corporation
IdentifiersCVE-2013-4786CWE-200

CVE-2013-4786 is an information disclosure weakness inherent in the IPMI 2.0 RMCP+ Authenticated Key-Exchange Protocol (RAKP). A vulnerable Baseboard Management Controller returns a RAKP message 2 HMAC-SHA1 value derived from the selected account password before the client has authenticated. The requester controls or knows the associated session values, enabling offline verification of password guesses against the captured response.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

An unauthenticated remote attacker can collect password-derived authentication material for valid BMC accounts and perform offline dictionary or brute-force recovery without generating repeated failed-login events on the target. Recovered BMC credentials can enable highly privileged out-of-band server administration, including power control, remote console and virtual-media access, firmware and low-level configuration changes, persistence below the operating system, and pivoting through inadequately segmented management networks.

Mitigation

If you can’t patch tonight, do this now.

Place BMC interfaces on dedicated, isolated management networks and permit access only from authorized administrative systems through tightly controlled paths such as VPNs or bastion hosts. Filter IPMI management traffic at network boundaries, disable anonymous accounts and weak authentication configurations, limit management-plane access with ACLs, and continuously monitor BMC inventory and management-network activity separately from ordinary host traffic.

Remediation

Patch, then assume compromise.

Remove IPMI-over-LAN exposure from untrusted networks and apply vendor firmware updates or configuration changes where available. Because the weakness originates in the IPMI 2.0 protocol design, a universal software patch is not available for all affected implementations. Replace factory, default, reused, weak, and predictably formatted BMC passwords with long, unique credentials; disable unused IPMI services and insecure legacy authentication options.

Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Intel CorporationIntelligent Platform Management Interfaceapplication
Oracle CorporationFujitsu M10 Firmwareoperating_system
FAQ

Frequently asked questions

Is CVE-2013-4786 exploited in the wild?
Yes. As of Oct 16, 2026, Mallory has reports of exploitation in the wild.
Is there a public exploit for CVE-2013-4786?
Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2013-4786, the earliest disclosed Oct 23, 2023.
Is there a patch for CVE-2013-4786?
Remove IPMI-over-LAN exposure from untrusted networks and apply vendor firmware updates or configuration changes where available. Because the weakness originates in the IPMI 2.0 protocol design, a universal software patch is not available for all affected implementations.
What products are affected by CVE-2013-4786?
Oracle Corporation Fujitsu M10 Firmware and Intel Corporation Intelligent Platform Management Interface.
How severe is CVE-2013-4786?
CVE-2013-4786 has a CVSS v3 score of 7.5 (High) and an EPSS score of 98.4% (100th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

39 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+7 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malware2Malware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity28Community discussion across Reddit, Mastodon, and other social sources.