CVE-2017-8987
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 Unauthenticated Remote Denial of Service vulnerability was identified in HPE Integrated Lights-Out 3 (iLO 3) version v1.88 only. The vulnerability is resolved in iLO3 v1.89 or subsequent versions.
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 confidenceAn unauthenticated remote attacker can cause a Denial of Service on HPE Integrated Lights-Out 3 (iLO 3) firmware version v1.88 by sending specially crafted requests to the management interface, rendering remote server management unavailable.
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= 1.88CVSS 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
- Changed
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/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.
-
Confirm HPE iLO 3 is presentAccess the server's management interface by navigating to the iLO web interface (typically https://<server-ip>/) or use command-line tools like 'hponcfg' or SNMP queries to verify the iLO 3 device is presentAffected if The system has an active HPE Integrated Lights-Out 3 management interface
-
Check iLO 3 firmware version via web interfaceLog into the iLO 3 web interface and navigate to the 'Information' or 'Overview' section under 'Summary' to view the firmware version displayed as 'iLO 3 Firmware Version'Affected if The displayed firmware version shows exactly v1.88 or 1.88
-
Check iLO 3 firmware version via CLIUse the HPE 'hponcfg' utility run: 'hponcfg -w /tmp/ilo_config.xml' then grep the output for 'FWVersion' or 'Firmware Version', or query via SNMP: 'snmpwalk -v2c -c <community> <iLO-ip> 1.3.6.1.4.1.11.2.3.9.1.1.1.0'Affected if The reported firmware version equals 1.88 or v1.88
-
Verify version is not remediatedIf firmware version 1.88 is found, confirm no subsequent patch has been applied by checking if versions 1.89 or higher are available in the 'Firmware Update' section of the iLO interfaceAffected if Firmware remains at version 1.88 with no upgrade to 1.89 or later recorded
The environment is affected if HPE iLO 3 firmware version 1.88 is actively running on the management interface.
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 dataUpgrade HPE iLO 3 firmware from version v1.88 to version v1.89 or subsequent versions to resolve the vulnerability.
- Consultation2.0 h
- Implementation1.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-8987 — 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-2017-8987 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