dbcve.org
Integrated Lights Out FirmwareOperating system · Hp

CVE-2013-4805

HIGH · 9.0 CVSS v2.0 Published 2013-08-05
Fix available
A fix is available. Upgrade to after 1.51a or later.
See remediation →
99/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 3 (aka iLO3) firmware before 1.60 and 4 (aka iLO4) firmware before 1.30 allows remote attackers to bypass authentication 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

Authentication bypass vulnerability in HP Integrated Lights-Out 3 (iLO3) firmware before version 1.60 and iLO4 firmware before version 1.30. The unspecified vulnerability allows remote unauthenticated attackers to bypass authentication in HP server remote management interfaces, potentially gaining full administrative control over the BMC.

MitigationUpdate iLO3 firmware to version 1.60 or later and iLO4 firmware to version 1.30 or later. Until patches are applied, restrict network access to iLO management interfaces using network segmentation or firewall rules to prevent unauthorized remote access.

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 FirmwareOperating system
Affected:<= 1.51a= 1.10= 1.15= 1.15a= 1.16a= 1.20a= 1.26a= 1.27a= 1.40a= 1.41a= 1.42a= 1.50

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

AV:N/AC:L/Au:N/C:P/I:P/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 the iLO hardware generation
    Access the server hardware documentation, BIOS, or HP management interface to determine if the system uses iLO3 or iLO4
    Affected if The system is identified as using HP iLO3 or iLO4 firmware
  2. Retrieve the installed iLO firmware version
    Use the HP iLO web interface, HPONCFG utility, or HP RESTful API to query the current firmware version from the BMC
    Affected if The firmware version cannot be determined or retrieved
  3. Compare iLO3 version against affected range
    For iLO3 systems, check if the installed version is 1.60 or later. Versions 1.50, 1.42a, 1.41a, 1.40a, 1.27a, 1.26a, 1.20a, 1.16a, 1.15a, 1.15, 1.10, and any version <=1.51a are affected
    Affected if The installed iLO3 firmware version is earlier than 1.60
  4. Compare iLO4 version against affected range
    For iLO4 systems, check if the installed version is 1.30 or later. Any version earlier than 1.30 is affected
    Affected if The installed iLO4 firmware version is earlier than 1.30
  5. Determine if remote iLO network access is enabled
    Check the iLO network settings to see if remote management access is enabled on the network interface
    Affected if Remote unauthenticated network access to iLO is enabled and the firmware version is in the affected range

A system is affected if it runs HP iLO3 firmware earlier than version 1.60 or iLO4 firmware earlier than version 1.30, with remote network access enabled.

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 1.51a
Interim mitigation

Update iLO3 firmware to version 1.60 or later and iLO4 firmware to version 1.30 or later. Until patches are applied, restrict network access to iLO management interfaces using network segmentation or firewall rules to prevent unauthorized remote access.

Recommended fix High confidence

HP iLO3 firmware version 1.60 or later; HP iLO4 firmware version 1.30 or later

  1. Identify the iLO firmware version currently installed on the affected HP server
  2. If running iLO3 firmware, determine if version is 1.51a or earlier, or versions 1.10, 1.15, or 1.15a
  3. If running iLO4 firmware, determine if version is earlier than 1.30
  4. Access the HP Support and Downloads page for your specific HP ProLiant server model
  5. Download the appropriate iLO firmware update package for your iLO version (iLO3 requires 1.60 or later; iLO4 requires 1.30 or later)
  6. Follow HP's firmware update procedures, typically using the HP Intelligent Provisioning or HP SUM (Smart Update Manager) utility
  7. Apply the firmware update in accordance with HP's instructions, ensuring stable power during the flashing process
  8. After update completion, verify the new firmware version meets the minimum security patch level (iLO3: 1.60+; iLO4: 1.30+)
Caveat Review HP firmware release notes for your specific ProLiant model for any compatibility considerations or known issues before applying firmware updates

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

Fix this in Integrated Lights Out Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-4805 — 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-2013-4805 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