dbcve.org
Integrated Lights Out 5 FirmwareOperating system · Hpe

CVE-2022-28633

HIGH · 7.3 CVSS v3.1 Published 2022-08-12
Fix available
A fix is available. Upgrade to 2.71 or later.
See remediation →
78/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 disclosure of sensitive information and a local unauthorized data modification vulnerability 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 read and write to the iLO 5 firmware file system resulting in a complete loss of confidentiality and a partial loss of 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 vulnerability in HPE Integrated Lights-Out 5 (iLO 5) firmware versions prior to 2.71 allows an unprivileged local user to read and write to the iLO firmware file system, resulting in complete loss of confidentiality and partial loss of integrity and availability.

MitigationUpdate HPE iLO 5 firmware to version 2.71 or later as provided by HPE 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
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
Low

CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L

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. Identify if the system uses HPE iLO 5
    Access the iLO web interface and navigate to the Overview page under System Information, or check the server's hardware documentation for iLO 5 branding
    Affected if The server is not equipped with HPE iLO 5 (it may be iLO 4 or a different management processor)
  2. Retrieve the installed iLO 5 firmware version
    Log into the iLO web interface and locate the firmware version displayed on the dashboard or under iLO Settings > Firmware, or use the command 'show /map1/firmwareinfo' via SSH connection to the iLO IP address
    Affected if Unable to retrieve the firmware version from iLO 5
  3. Compare the firmware version against the affected range
    Examine the displayed firmware version number and compare it to version 2.71. Note the full version string (for example, 2.50, 2.65, or 2.71)
    Affected if The installed firmware version is any version prior to 2.71 (for example, 2.60, 2.65, 2.40, etc.)
  4. Confirm the vulnerability is exploitable
    Verify that local user access to the iLO system exists. This vulnerability requires a local user with any privilege level to be present on the iLO system
    Affected if Local user accounts are configured on the iLO 5 device and the firmware version is below 2.71

The environment is affected if the installed HPE iLO 5 firmware version is lower than 2.71 and local user accounts exist on the iLO system.

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 iLO 5 firmware to version 2.71 or later as provided by HPE to remediate this vulnerability.

Recommended fix High confidence

iLO 5 firmware version 2.71

  1. 1. Navigate to HPE support website (support.hpe.com) and locate the iLO 5 firmware download section
  2. 2. Download the iLO 5 firmware version 2.71 or later for your specific HPE server model
  3. 3. Access the iLO 5 web interface using an administrator account
  4. 4. Navigate to the Firmware Updates section in the iLO web interface
  5. 5. Upload the downloaded firmware file and initiate the update process
  6. 6. Wait for the firmware update to complete and for iLO to restart
  7. 7. Verify the firmware version has been updated to 2.71 or later by checking the iLO web interface or using the iLO RESTful API

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
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,970
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,152.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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