CVE-2014-0860
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe firmware before 3.66E in IBM BladeCenter Advanced Management Module (AMM), the firmware before 1.43 in IBM Integrated Management Module (IMM), and the firmware before 4.15 in IBM Integrated Management Module II (IMM2) contains cleartext IPMI credentials, which allows attackers to execute arbitrary IPMI commands, and consequently establish a blade remote-control session, by leveraging access to (1) the chassis internal network or (2) the Ethernet-over-USB interface.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceIBM BladeCenter Advanced Management Module, Integrated Management Module, and IMM II firmware versions prior to 3.66E, 1.43, and 4.15 respectively contain cleartext IPMI credentials stored in the firmware. An attacker with access to the chassis internal network or Ethernet-over-USB interface can retrieve these credentials and execute arbitrary IPMI commands, enabling them to establish blade remote-control sessions.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 1.36all versions<= 3.65all versions<= 3.65all versionsCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the Management Module typeAccess the BMC/IPMI interface or check the hardware product documentation to determine if the system uses an IBM Advanced Management Module (AMM), Integrated Management Module (IMM), or Integrated Management Module II (IMM2).Affected if The system uses any of these IBM management modules.
-
Check AMM firmware versionFor Advanced Management Modules, access the web interface or use IPMI commands to retrieve the firmware version. Compare against the affected range of versions prior to 3.66E (versions <= 3.65).Affected if The AMM firmware version is 3.65 or earlier.
-
Check IMM firmware versionFor Integrated Management Modules, access the web interface or use IPMI commands to retrieve the firmware version. Compare against the affected range of versions prior to 1.43 (versions <= 1.36).Affected if The IMM firmware version is 1.36 or earlier.
-
Check IMM2 firmware versionFor Integrated Management Module II, access the web interface or use IPMI commands to retrieve the firmware version. Compare against the affected range of versions prior to 4.15 (versions <= 3.65).Affected if The IMM2 firmware version is 3.65 or earlier.
-
Assess network exposureVerify whether the chassis internal network or Ethernet-over-USB interface is accessible to untrusted users or networks. Check firewall rules and network segmentation around the BMC/IPMI interfaces.Affected if The management module is accessible over the internal network or Ethernet-over-USB to unauthorized parties.
A system is affected if it contains an IBM AMM, IMM, or IMM2 with firmware version within the vulnerable ranges AND that interface is network-accessible.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate affected firmware to version 3.66E (AMM), 1.43 (IMM), or 4.15 (IMM2) or later. Additionally, restrict network access to the chassis internal network and disable Ethernet-over-USB interfaces if not required.
- Consultation4.0 h
- Implementation6.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,064.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-0860 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2014-0860 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data