CVE-2022-28632
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 · uneditedA potential arbitrary code execution and a 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 exploit this vulnerability in an adjacent network 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. 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 confidenceAn unprivileged user on an adjacent network can exploit a vulnerability in HPE Integrated Lights-Out 5 (iLO 5) firmware versions prior to 2.71 to potentially execute arbitrary code within an isolated process, and also cause a denial of service in that isolated process.
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< 2.71CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify HPE iLO 5 presenceAccess the HPE iLO web interface via browser or use command-line tools like hponcfg or ilorest to query the device. iLO 5 is typically accessible on the BMC/IPMI interface of HPE servers.Affected if iLO 5 firmware is present and manageable on the system
-
Retrieve the installed iLO 5 firmware versionLog into the iLO web interface and navigate to the firmware information page, or use the hponcfg utility with the appropriate XML response file, or query via the iLO REST API at /redfish/v1/Managers/1. Record the displayed firmware version number.Affected if The displayed version is any version number less than 2.71 (for example, 2.60, 2.50, etc.)
-
Verify version is within affected rangeCompare the retrieved firmware version against the vulnerable range: any version prior to 2.71. Common vulnerable versions include 2.40, 2.50, 2.60, 2.65, 2.70.Affected if The installed version begins with 2.70, 2.65, 2.60, 2.50, 2.40 or any other version number less than 2.71
If the system has HPE iLO 5 firmware installed and the version is below 2.71, the environment is affected by this CVE.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2.71
Apply HPE iLO 5 firmware version 2.71 or later to address both the arbitrary code execution and DoS vulnerabilities in the isolated process.
iLO 5 firmware version 2.71 or later
- Download the HPE iLO 5 firmware version 2.71 or later from support.hpe.com
- Log in to the iLO 5 web interface with administrative privileges
- Navigate to the firmware update section (typically under 'Administration' > 'Firmware')
- Upload the downloaded firmware file (.bin)
- Initiate the firmware update and wait for completion
- After update completes, verify the iLO firmware version shows 2.71 or later in the web interface
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-28632 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-28632 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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