dbcve.org
Integrated Lights Out 3 FirmwareOperating system · Hp

CVE-2013-2338

HIGH · 10.0 CVSS v2.0 Published 2013-06-14
Fix available
A fix is available. Upgrade to after 1.55 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 on HP Integrated Lights-Out 3 (aka iLO3) cards with firmware before 1.57 and 4 (aka iLO4) cards with firmware before 1.22, when Single-Sign-On (SSO) is used, allows remote attackers to execute arbitrary code 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 · high confidence

HP Integrated Lights-Out 3 (iLO3) and iLO4 firmware before versions 1.57 and 1.22 respectively contain an unspecified vulnerability in the Single-Sign-On (SSO) functionality that allows remote unauthenticated attackers to execute arbitrary code. This critical flaw in the baseboard management controller (BMC) firmware enables complete compromise of affected servers over the network.

MitigationUpdate iLO3 firmware to version 1.57 or later and iLO4 firmware to version 1.22 or later. As an interim measure, disable the SSO functionality and ensure iLO management interfaces are not directly exposed to untrusted networks.

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 3 FirmwareOperating system
Affected:<= 1.55= 1.00= 1.05= 1.20= 1.26= 1.28= 1.50
Integrated Lights Out 4 FirmwareOperating system
Affected:<= 1.20= 1.11= 1.13

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 firmware version via web interface
    Log into the iLO web interface (https://<ilo-ip>) and navigate to the Overview or Administration > Firmware section to view the firmware version
    Affected if Version displayed is iLO3 <= 1.55, or iLO3 = 1.00/1.05/1.20/1.26/1.28/1.50, or iLO4 <= 1.20, or iLO4 = 1.11/1.13
  2. Identify iLO firmware version via command line
    Use the HP Lights-Out Configuration Utility (hponcfg) or the 'ilorest' command with 'ilorest login' followed by 'ilorest get Firmware' to retrieve the firmware version programmatically
    Affected if The reported firmware version falls within the affected ranges listed above
  3. Confirm iLO model generation
    Check whether the device is iLO3 or iLO4 by examining the firmware version string or the ILO web interface header - iLO3 versions typically start with 1.x while iLO4 versions start with 1.x as well but the hardware model differs
    Affected if The hardware is iLO3 or iLO4 and the version is in the affected list
  4. Verify SSO functionality status
    Access iLO web interface > Security > Authentication > Single Sign-On settings, or use 'ilorest list /oauth/sso' to check if SSO is enabled
    Affected if Single Sign-On (SSO) is enabled on the affected firmware version - the vulnerability requires SSO to be active

The system is affected if it runs HP iLO3 firmware version 1.55 or below (including 1.00, 1.05, 1.20, 1.26, 1.28, 1.50) or iLO4 firmware version 1.20 or below (including 1.11, 1.13) AND has SSO functionality 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.55
Interim mitigation

Update iLO3 firmware to version 1.57 or later and iLO4 firmware to version 1.22 or later. As an interim measure, disable the SSO functionality and ensure iLO management interfaces are not directly exposed to untrusted networks.

Recommended fix High confidence

HP iLO3 firmware >= 1.57; HP iLO4 firmware >= 1.22

  1. 1. Identify the exact iLO firmware version currently installed on the affected server by accessing the iLO web interface or using the HPONCFG/ilorest CLI tools
  2. 2. For iLO3: Download firmware version 1.57 or later from HP's support site (h20564.www2.hp.com)
  3. 3. For iLO4: Download firmware version 1.22 or later from HP's support site (h20564.www2.hp.com)
  4. 4. Upload the firmware file through the iLO web interface under Administration > Firmware, or use HP Smart Update Manager (SUM) or HPONCFG for batch updates
  5. 5. Restart the iLO when prompted after firmware update completes
  6. 6. Verify the new firmware version is installed and confirm SSO configuration is still functional
Caveat Firmware updates to iLO may require server downtime and iLO restart; ensure proper backup of iLO configuration and test in non-production environment first

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

Fix this in Integrated Lights Out 3 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-2338 — 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-2338 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