CVE-2018-7078
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 remote code execution was identified in HPE Integrated Lights-Out 4 (iLO 4) earlier than version v2.60 and HPE Integrated Lights-Out 5 (iLO 5) earlier than version v1.30.
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 remote code execution vulnerability affecting HPE Integrated Lights-Out 4 (iLO 4) versions prior to v2.60 and iLO 5 versions prior to v1.30. The vulnerability allows an attacker to execute arbitrary code on the affected iLO firmware, potentially compromising the baseboard management controller and the underlying server.
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.60< 1.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
- 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.
-
Access the iLO web interface to view firmware versionOpen a browser and navigate to the iLO IP address or hostname using HTTPS (https://<ilo-ip>). Log in with administrative credentials. The firmware version is displayed on the main dashboard or in the 'Information' section under 'Overview' or 'General' settings.Affected if The displayed firmware version is below 2.60 for iLO 4 or below 1.30 for iLO 5.
-
Check iLO firmware version via SSHConnect to the iLO using SSH (ssh <ilo-ip>) with administrative credentials. Once logged in, type 'info' or 'show /map1' to display firmware version information. The version is shown as the iLO firmware version.Affected if The reported firmware version is less than 2.60 for iLO 4 or less than 1.30 for iLO 5.
-
Query iLO version using the iLO RESTful APISend a GET request to https://<ilo-ip>/redfish/v1/Managers/Self using curl or a similar tool with basic authentication. The response JSON contains a 'FirmwareVersion' field under the iLO firmware information.Affected if The FirmwareVersion value is below 2.60 for iLO 4 or below 1.30 for iLO 5.
-
Check iLO firmware version from the host operating systemUse HPE tools such as 'hponcfg' (HPONCFG utility) or the HPE iLO cmdlet 'Get-HPiLOFirmwareVersion' on Windows, or 'ilorest' (iLO RESTful Interface Tool) on Linux. Run the appropriate command to retrieve the firmware version.Affected if The returned firmware version is less than 2.60 for iLO 4 or less than 1.30 for iLO 5.
If the installed iLO firmware version is below 2.60 (for iLO 4) or below 1.30 (for iLO 5), the system is affected by this 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.
From vendor data1.302.60
Update HPE iLO 4 firmware to version v2.60 or later, and iLO 5 firmware to version v1.30 or later. Apply the appropriate firmware patch through HPE's support website or management tools.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-7078 — 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-7078 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