CVE-2022-23701
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 remote host header injection security vulnerability has been identified in HPE Integrated Lights-Out 4 (iLO 4) firmware version(s): Prior to 2.60. This vulnerability could be remotely exploited to allow an attacker to supply invalid input to the iLO 4 webserver, causing it to respond with a redirect to an attacker-controlled domain. HPE has provided a firmware update to resolve this vulnerability in HPE Integrated Lights-Out 4 (iLO 4).
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 confidenceHost header injection vulnerability in HPE iLO 4 firmware prior to version 2.60 allows remote attackers to supply malicious Host HTTP headers to the iLO webserver, causing it to generate redirect responses pointing to attacker-controlled domains.
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.60CVSS 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
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
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 iLO 4 firmware version via web interfaceLog into the iLO 4 web interface using the iLO IP address and navigate to the Dashboard or Information > General page. Locate the firmware version field displayed as 'iLO 4' followed by a version number.Affected if The displayed firmware version is less than 2.60 (for example, 2.50, 2.40, or earlier).
-
Check iLO 4 firmware version via command lineRun the HPONCFG utility from the host operating system with the command 'hponcfg -g' to display the current iLO firmware version. Alternatively, query the iLO RESTful API at https://<ilo-ip>/redfish/v1/Managers/1 and read the 'FirmwareVersion' field.Affected if The retrieved firmware version is less than 2.60.
-
Confirm iLO 4 is the affected productVerify that the device is specifically HPE Integrated Lights-Out 4 (iLO 4) and not a different iLO generation (iLO 5, iLO 6). The product name is displayed in the iLO web interface header or in the hponcfg output.Affected if The product is iLO 4 and the firmware version is below 2.60.
If the installed HPE iLO 4 firmware version is any version prior to 2.60, the environment is affected by this host header injection vulnerability.
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.60
Update HPE Integrated Lights-Out 4 (iLO 4) firmware to version 2.60 or later to remediate the host header injection vulnerability.
iLO 4 firmware version 2.60
- Access the HPE iLO 4 web interface using an administrative account
- Navigate to the Firmware section in the iLO web interface
- Locate the firmware update option and upload the version 2.60 firmware file
- Confirm the firmware update and allow the process to complete
- Reboot the iLO 4 if prompted to complete the update
- Verify the installed firmware version shows 2.60 after the update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-23701 — 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-23701 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