dbcve.org
Integrated Lights Out 5 FirmwareOperating system · Hpe

CVE-2022-28634

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

A local arbitrary code execution vulnerability exists in HPE Integrated Lights-Out 5 (iLO 5) firmware versions prior to 2.71. A highly privileged local user could exploit this vulnerability to execute arbitrary code with full system privileges, resulting in complete loss of confidentiality, integrity, and availability.

MitigationApply HPE iLO 5 firmware version 2.71 or later to address this vulnerability. Schedule a maintenance window to perform the firmware update following HPE's documented upgrade procedures.

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. Check iLO 5 firmware version via web interface
    Log into the HPE iLO 5 web interface using a browser (https://<server-ip>/). Navigate to the 'Overview' or 'System Information' page. Locate the 'iLO Firmware Version' field displayed on that page.
    Affected if The displayed firmware version is any version earlier than 2.71 (for example, 2.60, 2.50, etc.)
  2. Check iLO 5 firmware version via HPONCFG utility
    Run the HPONCFG command-line utility on the host server: 'hponcfg -g' or 'hponcfg -v' to retrieve the current iLO firmware version. This requires administrator or root access to the host.
    Affected if The reported firmware version is below 2.71.
  3. Check iLO 5 firmware version via iLO RESTful API
    Send an HTTP GET request to the iLO REST API endpoint: 'https://<ilo-ip>/redfish/v1/Managers/Self'. Authenticate and retrieve the 'FirmwareVersion' value from the JSON response under the 'Manager' resource.
    Affected if The 'FirmwareVersion' value returned is less than 2.71.
  4. Check iLO 5 firmware version via HP iLO Online ROM Flash
    On the host server, run the HP iLO Online ROM Flash utility (iloromupd.exe or hpilo_firmware_*.bin) with a query flag, or view the installed firmware information in the HP SUM (Smart Update Manager) repository to confirm the iLO firmware version installed.
    Affected if The listed iLO firmware version is prior to 2.71.

If any detected iLO 5 firmware version is numerically less than 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 to address this vulnerability. Schedule a maintenance window to perform the firmware update following HPE's documented upgrade procedures.

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. Review HPE documentation for firmware update prerequisites and safety precautions
  3. Upload the firmware file through the iLO 5 web interface (Administration > Firmware) or using the HPE iLO RESTful API/CLI tools
  4. Initiate the firmware update and allow the process to complete - do not interrupt power to the server
  5. After the update completes, verify the iLO firmware version shows 2.71 or later in the web interface or via REST API
Caveat Standard firmware update risks apply - ensure adequate power backup and review HPE update guidelines before proceeding

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
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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