CVE-2017-8979
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 · uneditedSecurity vulnerabilities in the HPE Integrated Lights-Out 2 (iLO 2) firmware could be exploited remotely to allow authentication bypass, code execution, and denial of service.
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 confidenceMultiple critical vulnerabilities exist in HPE Integrated Lights-Out 2 (iLO 2) firmware that can be exploited remotely, enabling authentication bypass, arbitrary code execution, and denial of service conditions. The flaws likely involve improper input validation or authentication logic within the iLO 2 web interface and associated firmware components.
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.29CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/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.
-
Confirm HPE iLO 2 deviceAccess the device web interface via HTTPS or use HPE management tools (HPONCFG, hponcfg) or HP iLO RSS feed to identify the iLO hardware generationAffected if The device is not an HPE Integrated Lights-Out 2 (iLO 2) system
-
Retrieve iLO 2 firmware versionLog into the iLO 2 web interface and navigate to the Firmware Version section under the Information or Diagnostics tab, or use the 'HPONCFG' command-line utility with the '-g' flag to query firmware versionAffected if The installed firmware version is 2.29
-
Verify web interface is enabledCheck iLO 2 configuration via the web interface under Network Settings or by querying via HPONCFG to confirm the web server (HTTPS/HTTP) is enabledAffected if The iLO 2 web interface is enabled and accessible
-
Assess network exposureReview network segmentation and firewall rules to determine if the iLO 2 management interface is exposed to untrusted networks or the internetAffected if The iLO 2 web interface is reachable from untrusted network segments or directly from the internet
A user is affected if they have an HPE iLO 2 device running firmware version 2.29 with the web interface enabled and accessible.
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 dataApply the latest HPE iLO 2 firmware patch from HPE's support portal; if no patch is available due to iLO 2's end-of-life status, consider upgrading to a newer iLO generation or implementing network segmentation to restrict access to the management interface.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-8979 — 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-8979 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