CVE-2022-28629
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. A low privileged user could locally exploit this vulnerability to execute arbitrary code resulting in a complete loss of confidentiality, 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 confidenceHPE iLO 5 firmware versions prior to 2.71 contain a local arbitrary code execution vulnerability that allows a low-privileged local user to execute arbitrary code with elevated privileges, potentially achieving full system compromise.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Check installed iLO firmware versionAccess the iLO web interface, iLO REST API, or use HPE tools (such as hponcfg or iLO RESTful Interface Tool) to retrieve the current iLO 5 firmware version. This is typically found in the iLO dashboard or via command-line queries against the iLO subsystem.Affected if The installed firmware version is lower than 2.71 (for example, 2.60, 2.65, or any version in the 2.x range prior to 2.71).
-
Confirm product is HPE iLO 5Verify that the affected system uses HPE Integrated Lights Out 5 (iLO 5) and not an earlier iLO version. This can be confirmed via the iLO web interface or during the firmware version retrieval.Affected if The product is confirmed to be HPE iLO 5 firmware.
-
Determine if local user access existsReview system access controls and user accounts configured in iLO. This vulnerability requires a low-privileged local user to be present on the iLO subsystem.Affected if Local user accounts are configured on the iLO 5 device (the vulnerability allows such users to escalate privileges).
A system is affected if it runs HPE iLO 5 firmware version 2.70 or lower and has local user accounts configured.
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 remediate this vulnerability; verify the current iLO firmware version and schedule a maintenance window for the update.
iLO 5 firmware version 2.71 or later
- Download the iLO 5 firmware version 2.71 or later from support.hpe.com
- Log into the HPE iLO 5 web interface as an administrator
- Navigate to the 'Firmware' or 'Maintenance' section
- Select the firmware update option and upload the downloaded firmware file
- Confirm the installation and wait for the update to complete
- Reboot the server if prompted to ensure the new firmware is active
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-28629 — 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-28629 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