dbcve.org
Integrated Lights Out 5 FirmwareOperating system · Hpe

CVE-2022-28627

HIGH · 8.4 CVSS v3.1 Published 2022-08-12
Fix available
A fix is available. Upgrade to 2.71 or later.
See remediation →
89/100
Remediation priority · High
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
A local arbitrary code execution vulnerability was discovered in HPE Integrated Lights-Out 5 (iLO 5) firmware version(s): Prior to 2.71. An unprivileged 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

A local arbitrary code execution vulnerability in HPE Integrated Lights-Out 5 (iLO 5) firmware versions prior to 2.71 allows an unprivileged local user to execute arbitrary code with full system privileges, resulting in complete compromise of confidentiality, integrity, and availability.

MitigationApply HPE-provided firmware version 2.71 or later to all affected iLO 5 systems. Given this is a local privilege escalation with arbitrary code execution, prioritize patching systems with local user 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 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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/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. Identify iLO 5 firmware version
    Access the iLO web interface and navigate to the 'Overview' page, or use SSH to connect to the iLO and run the command 'show /map1/firmware1'. Alternatively, use the HPONCFG tool or iLO RESTful API to query the firmware version.
    Affected if The firmware version displayed is less than 2.71 (for example, 2.60, 2.50, etc.)
  2. Confirm iLO 5 is in use
    Verify that the affected device is running HPE Integrated Lights-Out 5 (iLO 5) specifically, not iLO 4 or iLO 6. This can be confirmed via the web interface header, CLI output showing 'iLO 5', or management documentation.
    Affected if The device uses iLO 5 firmware and the version is below 2.71
  3. Check for local user accounts
    Via the iLO web interface, navigate to 'Administration' > 'User Authentication' or use the CLI command 'show /map1/user1' to list configured local user accounts. Also check if directory authentication (like Active Directory) is in use instead of local accounts.
    Affected if Local user accounts are configured in iLO 5 (as opposed to external directory authentication only), because the vulnerability exploits a local user to gain privilege escalation

You are affected if your HPE iLO 5 firmware version is below 2.71 AND local user accounts are configured, allowing an unprivileged local user to potentially escalate to full system privileges.

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

Apply HPE-provided firmware version 2.71 or later to all affected iLO 5 systems. Given this is a local privilege escalation with arbitrary code execution, prioritize patching systems with local user access.

Recommended fix High confidence

iLO 5 firmware version 2.71 or later

  1. 1. Navigate to HPE support website (support.hpe.com) and locate the HPE iLO 5 firmware download page
  2. 2. Download the iLO 5 firmware version 2.71 or later for your specific HPE server model
  3. 3. Access the iLO web interface using an administrator account
  4. 4. Navigate to the firmware update section (typically under Administration > Firmware)
  5. 5. Upload and install the downloaded firmware file
  6. 6. Allow the firmware installation to complete - iLO will automatically restart
  7. 7. After iLO restarts, verify the firmware version is 2.71 or later by checking the iLO web interface overview page
Caveat Firmware updates may briefly interrupt iLO connectivity; ensure critical operations are not in progress before applying the update

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
  • 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-2022-28627 — 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-28627 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