dbcve.org
Integrated Lights Out 5 FirmwareOperating system · Hpe

CVE-2022-28636

HIGH · 7.4 CVSS v3.1 Published 2022-08-12
Fix available
A fix is available. Upgrade to 2.71 or later.
See remediation →
79/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 potential local arbitrary code execution and a local denial of service (DoS) vulnerability within an isolated process were 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 potentially execute arbitrary code in an isolated process resulting in a complete loss of confidentiality, integrity, and availability within that process. In addition, an unprivileged user could exploit a denial of service (DoS) vulnerability in an isolated process resulting in a complete loss of availability within that process. A successful attack depends on conditions beyond the attackers control. 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 · moderate confidence

Local arbitrary code execution and DoS vulnerability in HPE iLO 5 firmware (prior to 2.71) allows an unprivileged user to potentially execute arbitrary code in an isolated process, causing complete loss of confidentiality, integrity, and availability within that process.

MitigationUpdate HPE Integrated Lights-Out 5 (iLO 5) firmware to version 2.71 or later to remediate this vulnerability.

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

CVSS:3.1/AV:L/AC:H/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. Access iLO 5 web interface
    Log into the HPE iLO 5 web interface using browser (https://<server-ip>/) and navigate to the 'Information' or 'Overview' page to view firmware version
    Affected if Firmware version displayed is less than 2.71 (for example, 2.60, 2.50, etc.)
  2. Check iLO 5 version via SSH
    Connect to iLO 5 via SSH using a client (ssh <ilo-ip>) and run command 'info' or 'show /map1/firmware0' to retrieve firmware version
    Affected if Version shown is prior to 2.71
  3. Query iLO 5 via HPONCFG
    Run HPONCFG utility on the host server: 'hponcfg -g' or 'hponcfg -a -w hponcfg.out' to get iLO firmware information
    Affected if Firmware version in output is below 2.71
  4. Check via HPE iLO RESTful API
    Send GET request to https://<ilo-ip>/redfish/v1/Managers/1, using curl or similar, and parse 'FirmwareVersion' field in JSON response
    Affected if FirmwareVersion value is less than 2.71

Your environment is affected if the HPE iLO 5 firmware version is below 2.71 (any version 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 Integrated Lights-Out 5 (iLO 5) firmware to version 2.71 or later to remediate this vulnerability.

Recommended fix High confidence

iLO 5 firmware version 2.71

  1. Check current iLO 5 firmware version via the iLO web interface or using the `ilorest` command-line tool
  2. Navigate to the HPE support site (support.hpe.com) and search for iLO 5 firmware version 2.71 or later
  3. Download the firmware update file for your specific HPE server model
  4. Access the iLO web interface, go to the 'Firmware' section, and upload the new firmware image
  5. Follow the on-screen prompts to complete the firmware update; the iLO may automatically reboot during the process
  6. After the update completes, verify the installed firmware version shows 2.71 or later
Caveat No breaking changes documented in the available advisory information

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
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,820
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,912.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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