dbcve.org
Integrated Lights Out 5 FirmwareOperating system · Hpe

CVE-2022-28638

HIGH · 7.8 CVSS v3.1 Published 2022-09-20
Fix available
A fix is available. Upgrade to 2.72 or later.
See remediation →
80/100
Remediation priority · High
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
An isolated local disclosure of information and potential isolated local 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 · moderate confidence

A local vulnerability in HPE iLO 5 firmware version 2.71 allows an attacker with local access to potentially disclose sensitive information and execute arbitrary code, impacting confidentiality, integrity, and availability of the management controller.

MitigationApply HPE's updated firmware for iLO 5 to address the vulnerability; restrict physical and local access to server management interfaces to limit exposure.

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

CVSS:3.1/AV:L/AC:L/PR:L/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. Verify HPE iLO 5 is present
    Access the iLO web interface via browser or run the `ilorest` tool or HPONCFG utility to query the management controller. Look for indicators that the system uses HPE Integrated Lights Out 5.
    Affected if The system does not use HPE iLO 5 as its management controller
  2. Check iLO firmware version
    In the iLO web interface, navigate to the Overview or Information page to view the firmware version. Alternatively, use the command `ilorest get firmware --json` or `hponcfg -g` to retrieve the installed firmware version.
    Affected if The installed firmware version is below 2.72 (for example, 2.71 or earlier)
  3. Assess local access exposure
    Determine whether physical access to the server or local console access to the iLO management interface is possible by unauthorized or untrusted users.
    Affected if Untrusted users can gain local or physical access to the iLO management interface or server console

A user is affected if their system runs HPE iLO 5 firmware version 2.71 or earlier and local or physical access to the management interface is available to untrusted individuals.

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 firmware for iLO 5 to address the vulnerability; restrict physical and local access to server management interfaces to limit exposure.

Recommended fix High confidence

iLO 5 Firmware version 2.72 or later

  1. Navigate to the HPE support site (support.hpe.com) and locate the HPE Integrated Lights-Out 5 (iLO 5) firmware downloads section
  2. Locate and download the iLO 5 firmware version 2.72 or later for your specific HPE server model
  3. Access the iLO web interface using an administrative account
  4. Navigate to the Firmware section under Administration or Maintenance
  5. Upload the downloaded firmware file (.bin or .flm format) to the iLO subsystem
  6. Initiate the firmware update and allow the process to complete - do not interrupt power or network during this process
  7. After the update completes, verify the iLO firmware version displays 2.72 or later in the iLO web interface
Caveat Firmware updates may require a brief server reboot and may temporarily interrupt remote management access; ensure maintenance window is scheduled

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
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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