CVE-2018-7093
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 3 prior to v1.90, iLO 4 prior to v2.60, iLO 5 prior to v1.30, Moonshot Chassis Manager firmware prior to v1.58, and Moonshot Component Pack prior to v2.55 could be remotely exploited to create a 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 confidenceA remote denial of service vulnerability in HPE Integrated Lights-Out (iLO) firmware allows attackers to crash the remote management interface, rendering server hardware management inaccessible.
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.90< 2.60< 1.30< 1.58< 2.55CVSS 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.
-
Access iLO firmware version via web interfaceLog into the iLO web interface (https://<server-ip>/) and navigate to the 'Administration' or 'Information' section to view the iLO firmware version displayed on the main dashboard or in the Firmware section.Affected if The displayed firmware version is below 1.90 for iLO 3, below 2.60 for iLO 4, below 1.30 for iLO 5, below 1.58 for Moonshot Chassis Manager, or below 2.55 for Moonshot Component Pack.
-
Identify iLO generation via CLIConnect to iLO via SSH using an administrative account and run the command 'show /map1/firmware1' or 'iRMC IPMI or similar command to retrieve firmware details. The output will show the firmware version and can also indicate the iLO generation (iLO3, iLO4, iLO5).Affected if The firmware version output shows a version number lower than the thresholds listed in step 1.
-
Check iLO version using HP management toolsUse HP Smart Update Manager (HP SUM), hpqlocfg, or hponcfg to query the iLO firmware version remotely. These tools can be run from a management station to pull firmware inventory across multiple servers.Affected if The version retrieved is less than 1.90 (iLO3), 2.60 (iLO4), 1.30 (iLO5), 1.58 (Moonshot Chassis Manager), or 2.55 (Moonshot Component Pack).
A system is affected if the installed HPE iLO or Moonshot firmware version falls below the specific version threshold for its product line.
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.301.581.90
Update HPE iLO firmware to version 1.90 or later for iLO 3, version 2.60 or later for iLO 4, and version 1.30 or later for iLO 5; Moonshot Chassis Manager should be updated to v1.58 or later, and Moonshot Component Pack to v2.55 or later.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-7093 — 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-7093 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