CVE-2022-23704
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 security vulnerability has been identified in Integrated Lights-Out 4 (iLO 4). The vulnerability could allow remote Denial of Service. The vulnerability is resolved in Integrated Lights-Out 4 (iLO 4) 2.80 and later.
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 · moderate confidenceA remote denial-of-service vulnerability in HP Integrated Lights-Out 4 (iLO 4) firmware allows unauthenticated attackers to potentially disrupt the server management interface. The vulnerability has a CVSS base score of 7.5 (HIGH), indicating network-exploitable DoS with no authentication required.
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.80CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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.
-
Access the iLO 4 web interfaceOpen a browser and navigate to the iLO 4 IP address (usually the BMC/IPMI IP). Log in or attempt to access the homepage without authentication. Check the firmware version displayed on the login page or in the 'Integrated Management Log' or 'Information' section under ' firmware version'.Affected if The displayed firmware version is less than 2.80 or shows a version string indicating a build prior to 2.80
-
Check iLO firmware version via command lineUse the HP Lights-Out Configuration Utility (hponcfg) or ILO CLI tools if you have host access: run 'hponcfg -g' or 'ilorest' with the appropriate flags to retrieve the current iLO firmware version. Alternatively, check via SNMP using 'snmpwalk' on the iLO OID for firmware version.Affected if The reported firmware version is below 2.80
-
Verify iLO 4 is the active management interfaceConfirm the target system uses HP Integrated Lights-Out 4 (iLO 4) and not a different iLO generation (iLO 5 or iLO 6). Check server model and iLO branding in the web UI or via 'ilorest list' to confirm iLO 4 is present.Affected if The system has iLO 4 and the firmware version is below 2.80
If HP iLO 4 firmware version is confirmed to be less than 2.80, the system is vulnerable to this unauthenticated remote denial-of-service flaw.
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.80
Upgrade iLO 4 firmware to version 2.80 or later to remediate this vulnerability.
iLO 4 firmware version 2.80 or later
- Download the iLO 4 firmware version 2.80 or later from HPE support website (support.hpe.com)
- Access the iLO 4 web interface using an administrator account
- Navigate to the firmware update section
- Upload and apply the iLO 4 firmware version 2.80 or later
- Allow the firmware update to complete - iLO will automatically reboot
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation3.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-23704 — 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-23704 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