CVE-2022-28631
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 confidenceA vulnerability in HPE iLO 5 firmware prior to version 2.71 allows an unprivileged user on an adjacent network to potentially execute arbitrary code within an isolated process, compromising confidentiality, integrity, and availability of that process. A separate denial of service vulnerability in the same isolated process can also be exploited.
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 firmware versionAccess the iLO web interface and navigate to the Administration > General page, or connect via SSH and run the 'info' command to display firmware version informationAffected if The displayed firmware version is below 2.71 (for example, 2.70, 2.63, etc.)
-
Confirm product is HPE iLO 5Verify the product name in the iLO web interface header or via the 'info' command output shows 'Integrated Lights-Out 5' or 'iLO 5'Affected if The product is not HPE iLO 5 (such as iLO 4 or iLO 3, which are different products)
-
Verify iLO network accessibilityCheck if iLO is accessible on the network from an adjacent network segment. This may require reviewing network firewall rules or VLAN configurations that allow access to the iLO management interfaceAffected if iLO management interface is exposed to an adjacent (non-management) network segment without proper network segmentation
You are affected if your HPE iLO 5 firmware version is below 2.71 and the iLO interface is network-accessible, allowing an adjacent network attacker to reach the management interface.
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
Update HPE iLO 5 firmware to version 2.71 or later to address both the arbitrary code execution and DoS vulnerabilities.
iLO 5 firmware version 2.71
- Obtain the iLO 5 firmware version 2.71 or later from HPE support (support.hpe.com)
- Access the HPE iLO 5 web interface or use the iLO RESTful API
- Navigate to the firmware update section in the iLO management interface
- Upload and install the firmware version 2.71 or later
- Reboot the iLO management processor if required to complete the update
- Verify the installed firmware version shows 2.71 or later after the update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,488.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-28631 — 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-28631 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