CVE-2018-7105
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 security vulnerability in HPE Integrated Lights-Out 5 (iLO 5) for HPE Gen10 Servers prior to v1.35, HPE Integrated Lights-Out 4 (iLO 4) prior to v2.61, HPE Integrated Lights-Out 3 (iLO 3) prior to v1.90 could be remotely exploited to execute arbitrary code leading to disclosure of information.
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 confidenceA remote code execution vulnerability exists in HPE Integrated Lights-Out (iLO) firmware for Gen10 (iLO 5), Gen9 (iLO 4), and earlier (iLO 3) servers. Attackers can exploit this to execute arbitrary code and disclose information. The vulnerability stems from insufficient input validation in the iLO web interface.
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.35< 1.90< 2.61CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:H/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.
-
Identify iLO generation and versionAccess the iLO web interface by browsing to the server's iLO IP address (typically on the dedicated iLO network port). Login and view the iLO firmware version displayed on the main dashboard or under 'Administration' > 'Firmware'. Alternatively, use HP's 'hponcfg' utility from the host OS: 'hponcfg -g' to retrieve iLO firmware information.Affected if The displayed firmware version is below 1.35 for iLO 5, below 2.61 for iLO 4, or below 1.90 for iLO 3.
-
Confirm iLO web interface is enabledIn the iLO web interface, navigate to 'Administration' > 'Access Settings' > 'Web Server' and verify that the web interface is enabled. The vulnerability resides in the web interface, so it is only exploitable if this interface is active.Affected if The web interface is enabled and the firmware version falls within the affected ranges.
-
Check iLO network accessibilityFrom an external system, verify whether the iLO web interface port (default HTTPS port 443) is reachable on the iLO IP address. Use: 'nmap -p 443 <iLO_IP>' or 'curl -k https://<iLO_IP>/' to test connectivity.Affected if The iLO web interface is network-accessible and the firmware version is vulnerable.
You are affected if your HPE iLO firmware version (iLO 5 < 1.35, iLO 4 < 2.61, or iLO 3 < 1.90) is running with the web interface enabled and accessible on the network.
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 data1.351.902.61
Update iLO firmware to versions iLO 5 v1.35+, iLO 4 v2.61+, or iLO 3 v1.90+ as applicable. Schedule maintenance window for firmware deployment and verify post-update functionality.
- Consultation4.0 h
- Implementation4.0 h
- Testing3.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,728.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-7105 — 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-2018-7105 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