dbcve.org
Integrated Lights Out 5 FirmwareOperating system · Hpe

CVE-2022-28639

HIGH · 8.8 CVSS v3.1 Published 2022-09-20
Fix available
A fix is available. Upgrade to 2.72 or later.
See remediation →
93/100
Remediation priority · Urgent
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 remote potential adjacent denial of service (DoS) and potential adjacent arbitrary code execution vulnerability that could potentially lead to a loss of confidentiality, integrity, and availability were discovered in HPE Integrated Lights-Out 5 (iLO 5) in Version: 2.71. Hewlett Packard Enterprise has provided updated firmware for HPE Integrated Lights-Out 5 (iLO 5) that addresses these security vulnerabilities.

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 remote adjacent network vulnerability in HPE iLO 5 firmware version 2.71 allows potential adjacent attackers to cause denial of service and potentially execute arbitrary code on the BMC, compromising server management functions.

MitigationApply HPE's updated iLO 5 firmware patch to address the vulnerability. Schedule during maintenance window as BMC firmware updates may temporarily disrupt remote management connectivity.

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.72

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

CVSS:3.1/AV:A/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. Confirm HPE iLO 5 is present
    Access the iLO web interface by entering the iLO IP address in a browser, or query the iLO REST API at https://<ilo-ip>/redfish/v1/Managers/1, or run 'hponcfg' or 'ilorest' from the host OS to retrieve iLO information
    Affected if The system does not have iLO 5 (e.g., has iLO 4 or no iLO) - this CVE only affects iLO 5
  2. Retrieve the iLO 5 firmware version
    In the iLO web interface, navigate to the Dashboard or Overview page and locate the Firmware Version field. Via command line, use 'ilorest list /Managers/1' or 'hponcfg -g' to retrieve the firmware version
    Affected if Unable to retrieve a firmware version indicates iLO may not be accessible or functional
  3. Compare installed version to affected range
    Take the retrieved firmware version (e.g., displayed as something like 2.70, 2.71, 2.65) and compare it numerically to version 2.72. Any version lower than 2.72 is affected
    Affected if Firmware version is less than 2.72 (for example, 2.71, 2.70, 2.65, etc.) - the system is vulnerable
  4. Verify iLO network accessibility
    Confirm the iLO dedicated network port or shared network port is reachable on the network by pinging the iLO IP address or checking network configuration in the iLO web interface under Network Settings
    Affected if iLO is network-accessible from untrusted adjacent networks - combined with version < 2.72, the vulnerability is exploitable

The system is affected by CVE-2022-28639 if it runs HPE iLO 5 firmware version lower than 2.72 and has network accessibility to the iLO interface.

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.72 or later
Fixed in 2.72
Interim mitigation

Apply HPE's updated iLO 5 firmware patch to address the vulnerability. Schedule during maintenance window as BMC firmware updates may temporarily disrupt remote management connectivity.

Recommended fix High confidence

iLO 5 Firmware version 2.72 or later

  1. Log into the HPE iLO 5 web interface or use iLO RESTful API to check the current firmware version
  2. Navigate to the Firmware section in iLO web interface or use HPE iLO Repository for firmware updates
  3. Download the iLO 5 firmware version 2.72 or later from support.hpe.com
  4. Upload the firmware file through the iLO web interface (Administration > Firmware) or use iLO RESTful API/ROM Flash Utility
  5. Initiate the firmware update and allow the process to complete; iLO will automatically reset during the update
  6. Verify the firmware version has been updated to 2.72 or later after the reset
Caveat Firmware updates may cause temporary iLO unavailability during the update process; ensure proper backup of iLO configuration and verify compatibility with managed server before applying

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
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,440
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,304.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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