dbcve.org
Integrated Lights Out 5 FirmwareOperating system · Hpe

CVE-2022-28626

MEDIUM · 6.7 CVSS v3.1 Published 2022-08-12
Fix available
A fix is available. Upgrade to 2.71 or later.
See remediation →
69/100
Remediation priority · Elevated
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
A local arbitrary code execution vulnerability was discovered in HPE Integrated Lights-Out 5 (iLO 5) firmware version(s): Prior to 2.71. A highly privileged user could locally exploit this vulnerability to execute arbitrary code resulting in a complete loss of confidentiality, integrity, and availability. HPE has provided a firmware update to resolve this vulnerability in HPE Integrated Lights-Out 5 (iLO 5).

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

Local arbitrary code execution vulnerability in HPE Integrated Lights-Out 5 (iLO 5) firmware versions prior to 2.71. A highly privileged authenticated user can exploit this flaw to execute arbitrary code with the highest privileges, resulting in complete compromise of confidentiality, integrity, and availability of the iLO management subsystem.

MitigationUpdate HPE iLO 5 firmware to version 2.71 or later to remediate this vulnerability. As the vulnerability requires a highly privileged user, ensure proper access controls and monitor for unauthorized privileged accounts.

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 5 FirmwareOperating system
Affected:< 2.71

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
Local
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

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. Access iLO 5 web interface
    Navigate to the iLO IP address via HTTPS (e.g., https://[server-ilo-ip]) and log in with administrative credentials. Check the home page or 'Overview' section for the firmware version information.
    Affected if The displayed firmware version is earlier than 2.71 (e.g., 2.60, 2.50, etc.)
  2. Query iLO 5 via REST API
    Use a tool like curl to query the iLO RESTful Interface. Send a GET request to https://[ilo-ip]/redfish/v1/Managers/1 with authentication and inspect the 'FirmwareVersion' field in the JSON response.
    Affected if The 'FirmwareVersion' value returned is less than 2.71
  3. Use HPE iLO RESTful Interface Tool (ilorest)
    Run 'ilorest login [ilo-ip] -u [username] -p [password]' followed by 'ilorest manager' to retrieve manager details including the firmware version.
    Affected if The reported iLO firmware version is below 2.71
  4. Check via hponcfg utility
    If HPE tools are installed on the managed server, run 'hponcfg -g' to display current iLO configuration including the firmware version.
    Affected if The firmware version shown is prior to 2.71

You are affected if your HPE iLO 5 firmware version is below 2.71, as the arbitrary code execution vulnerability applies to all versions prior to 2.71.

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 2.71 or later
Fixed in 2.71
Interim mitigation

Update HPE iLO 5 firmware to version 2.71 or later to remediate this vulnerability. As the vulnerability requires a highly privileged user, ensure proper access controls and monitor for unauthorized privileged accounts.

Recommended fix High confidence

HPE iLO 5 firmware version 2.71 or later

  1. Log into the HPE iLO 5 web interface or use the HPE iLO RESTful API to identify the current firmware version
  2. Navigate to HPE support website (support.hpe.com) and search for iLO 5 firmware version 2.71 or later for your specific HPE server model
  3. Download the iLO 5 firmware update file from HPE support
  4. Upload the firmware file through the iLO 5 web interface (Navigate to Administration > Firmware > Update) or using the HPE iLO RESTful API or iLO RIBCL scripting tools
  5. Apply the firmware update and wait for the installation to complete
  6. Reboot the server or reset iLO 5 as prompted by the update process
  7. Verify the iLO 5 firmware has been updated to version 2.71 or later by checking the firmware version in the iLO 5 web interface

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

Fix this in Integrated Lights Out 5 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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