CVE-2015-5436
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 with HP Integrated Lights-Out 4 (iLO 4) firmware version 2.11 and later, but prior to version 2.30. The vulnerability could be exploited remotely resulting in Denial of Service (DoS). Note this was originally published in 2015 however the CVE entry was added in 2020.
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 confidenceThis is a Denial of Service vulnerability in HP Integrated Lights-Out 4 (iLO 4) remote management firmware. The flaw exists in versions 2.11 through 2.29 and can be exploited remotely to cause the iLO management interface to become unavailable, potentially disrupting server remote administration capabilities.
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.30CVSS 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.
-
Verify HP iLO 4 is present on the systemAccess the iLO web interface by navigating to the server's IP address (commonly in the BMC/IPMI network range) via HTTPS. Look for the iLO login page. Alternatively, connect via SSH to the iLO IP and run the 'show' command to display iLO information.Affected if The system does not have an iLO 4 interface - this CVE only applies to HP iLO 4 hardware.
-
Retrieve the iLO firmware versionIn the iLO web interface, log in and navigate to the main Dashboard or Information > Overview page. The firmware version is displayed prominently. Via CLI (SSH), run the command 'show /map1/firmware' or 'firmware version' to display the installed firmware version.Affected if Unable to retrieve version - verify network connectivity to iLO and proper credentials.
-
Compare installed version against affected rangeNote the firmware version displayed (for example: 2.11, 2.20, 2.25, 2.29). Compare this version number to the affected range of 2.11 through 2.29. Versions below 2.30 are vulnerable. Versions 2.30 and later are patched.Affected if The installed firmware version falls between 2.11 and 2.29 inclusive - the system is vulnerable to CVE-2015-5436.
A system is affected if it has HP iLO 4 with firmware version 2.11 through 2.29 installed; version 2.30 or later is not affected.
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.
From vendor data2.30
Upgrade HP iLO 4 firmware to version 2.30 or later to remediate this vulnerability. Organizations should verify current firmware version on affected systems and schedule maintenance windows for the update.
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-5436 — 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-2015-5436 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