CVE-2022-28630
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 local arbitrary code execution vulnerability was 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 execute arbitrary code resulting in a complete loss of confidentiality and integrity, and a partial loss of availability. User interaction is required to exploit this vulnerability. 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 local arbitrary code execution vulnerability in HPE Integrated Lights-Out 5 (iLO 5) firmware versions prior to 2.71 allows an unprivileged user to execute arbitrary code with full compromise of confidentiality and integrity, though user interaction is required for exploitation.
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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- Low
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify HPE iLO 5 presenceAccess the iLO web interface by entering the server's iLO IP address in a browser, or use the HPE iLO REST API/CLI tools (hponcfg, ilorest) to query the iLO subsystem.Affected if The system has HPE iLO 5 firmware installed.
-
Retrieve the iLO firmware versionIn the iLO web interface, navigate to the 'Information' or 'Overview' page under 'iLO 5' to view the firmware version. From CLI, run 'hponcfg -g' or use 'ilorest login <iLO_IP> -u <user> -p <pass> && ilorest info' to query the firmware version.Affected if You can retrieve the firmware version number.
-
Compare version against CVE thresholdCompare the installed firmware version to version 2.71. Note the full version string (e.g., 2.60, 2.65, 2.70) and check if it is less than 2.71.Affected if The installed iLO 5 firmware version is any version prior to 2.71 (for example: 2.60, 2.65, 2.70, 2.70_rev).
A system is affected if HPE iLO 5 firmware is installed and the version number is less than 2.71.
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 remediate this vulnerability.
iLO 5 firmware version 2.71 or later
- Obtain the iLO 5 firmware version 2.71 or later from HPE support.hpe.com or the HPE Software Depot
- Log into the HPE iLO 5 web interface as an administrator
- Navigate to the Firmware Updates section
- Upload and install the new firmware version 2.71 or later
- Verify the firmware installation was successful by checking the iLO version in the web interface
- Reboot the server if required by the firmware update process
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing3.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,728.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-28630 — 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-28630 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