dbcve.org
Integrated Lights Out 2 FirmwareOperating system · Hp

CVE-2014-7876

HIGH · 10.0 CVSS v2.0 Published 2015-03-31
Fix available
A fix is available. Upgrade to after 2.25 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Unspecified vulnerability in HP Integrated Lights-Out (iLO) firmware 2 before 2.27 and 4 before 2.03 and iLO Chassis Management (CM) firmware before 1.30 allows remote attackers to gain privileges, execute arbitrary code, or cause a denial of service via unknown vectors.

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 · moderate confidence

Critical pre-authentication vulnerability in HP Integrated Lights-Out (iLO) remote management firmware allows remote unauthenticated attackers to execute arbitrary code, escalate privileges, or cause denial of service. The vulnerability is present in iLO 2 versions before 2.27, iLO 4 versions before 2.03, and iLO Chassis Management firmware before 1.30.

MitigationApply vendor firmware updates: upgrade iLO 2 to version 2.27 or later, iLO 4 to version 2.03 or later, and iLO CM to version 1.30 or later. If patching is not immediately possible, restrict network access to iLO management interfaces.

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
Integrated Lights Out 2 FirmwareOperating system
Affected:<= 2.25
Integrated Lights Out 4 FirmwareOperating system
Affected:<= 2.01
Integrated Lights Out Chassis Management FirmwareOperating system
Affected:<= 1.29

CVSS 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
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify iLO network exposure
    Scan your network for devices listening on port 443 (HTTPS) or 80 (HTTP) on management IP addresses. Check firewall rules and network segments for iLO management interfaces. HP iLO typically uses dedicated NICs or shared network ports on HP servers.
    Affected if iLO management interfaces are directly accessible from untrusted networks without firewall filtering
  2. Access iLO web interface to retrieve firmware version
    Navigate to the iLO IP address via HTTPS in a web browser. Log in with administrative credentials. The firmware version is displayed on the main dashboard or in the Administration > Firmware section.
    Affected if The displayed firmware version is 2.25 or lower for iLO 2, 2.01 or lower for iLO 4, or 1.29 or lower for iLO Chassis Management
  3. Check iLO version via SSH
    Connect to the iLO IP address via SSH (port 22). Log in with administrative credentials. Run the command 'show /map1/firmware1' or 'version' to display the installed firmware version.
    Affected if The reported firmware version falls within the vulnerable ranges: iLO 2 <= 2.25, iLO 4 <= 2.01, or iLO CM <= 1.29
  4. Query firmware version using HPONCFG
    On the host server, run the HPONCFG utility (hpnsql or similar) to query iLO firmware information. Execute: 'hponcfg -g' or use the iLO RDF (Remote Director) interface if available, to retrieve the firmware version programmatically.
    Affected if HPONCFG reports a firmware version that matches the vulnerable version ranges listed above

Your environment is affected if any HP iLO device (iLO 2, iLO 4, or iLO Chassis Management) with firmware version at or below the vulnerable thresholds is network-accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 2.25
Interim mitigation

Apply vendor firmware updates: upgrade iLO 2 to version 2.27 or later, iLO 4 to version 2.03 or later, and iLO CM to version 1.30 or later. If patching is not immediately possible, restrict network access to iLO management interfaces.

Recommended fix High confidence

iLO 2: firmware >= 2.27 | iLO 4: firmware >= 2.03 | iLO CM: firmware >= 1.30

  1. 1. Identify the specific HP iLO device model (iLO 2, iLO 4, or iLO Chassis Management) in your environment
  2. 2. Download the appropriate HP iLO firmware update from the official HP support website (h20564.www2.hp.com)
  3. 3. For iLO 2: Upgrade firmware to version 2.27 or later
  4. 4. For iLO 4: Upgrade firmware to version 2.03 or later
  5. 5. For iLO Chassis Management: Upgrade firmware to version 1.30 or later
  6. 6. Follow HP's standard firmware update procedure, which typically involves uploading the firmware through the iLO web interface or using the HP SUM (Smart Update Manager) tool
  7. 7. After upgrade, verify the firmware version matches the target fixed release
  8. 8. Test that iLO functionality (remote console, virtual media, power management) operates normally
Caveat Firmware updates may require server downtime; verify compatibility with server hardware model before applying

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Integrated Lights Out 2 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-7876 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2014-7876 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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