dbcve.org
Integrated Lights Out 5 FirmwareOperating system · Hpe

CVE-2022-28628

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, achieving full system compromise with complete loss of confidentiality, integrity, and availability.

MitigationApply HPE iLO 5 firmware version 2.71 or later by downloading from HPE support and updating through the iLO management interface.

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. Determine iLO 5 firmware version via web interface
    Log in to the iLO web interface using the server's iLO IP address and credentials. Navigate to the Dashboard or Information > General section to view the firmware version listed as 'iLO 5' or 'Integrated Lights-Out'.
    Affected if The displayed firmware version is a number less than 2.71 (for example, 2.60, 2.50, or any version before 2.71).
  2. Determine iLO 5 firmware version via iLO RESTful API
    Send an HTTP GET request to the iLO RESTful API endpoint at https://<ilo-ip>/redfish/v1/Managers/1, using appropriate authentication. Locate the 'FirmwareVersion' or 'iLO Version' field in the JSON response.
    Affected if The firmware version returned is less than 2.71.
  3. Determine iLO 5 firmware version via command line from host OS
    Use an HPE management command line tool such as hpasmcli, hponcfg, or the PowerShell HPEiLOCmdlets module (Get-HPEiLOLog) to query the iLO firmware version from the operating system running on the managed server.
    Affected if The reported iLO firmware version is a value below 2.71.
  4. Determine iLO 5 firmware version during server POST
    During server boot, observe the POST (Power-On Self-Test) screen or press the appropriate key (often F8 or F9) to enter the iLO configuration utility. The firmware version is displayed in the main screen or under the System Information section.
    Affected if The iLO firmware version shown is any version prior to 2.71.

If the installed HPE iLO 5 firmware version is below 2.71, the system is affected by this vulnerability.

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 iLO 5 firmware version 2.71 or later by downloading from HPE support and updating through the iLO management interface.

Recommended fix High confidence

iLO 5 firmware version 2.71

  1. Download the iLO 5 firmware version 2.71 or later from support.hpe.com
  2. Access the HPE iLO 5 web interface or use the HPE iLO RESTful API to upload and apply the firmware update
  3. Follow HPE's standard firmware upgrade procedure for iLO 5, ensuring stable power during the update process
  4. After the firmware update completes, verify the iLO 5 firmware version is 2.71 or later via the web interface or iLO RDFW CLI
  5. Confirm the vulnerability is resolved by checking that the iLO 5 firmware version displayed matches the fixed release

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
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
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,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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