CVE-2018-7118
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 local access restriction bypass vulnerability was identified in HPE Service Pack for ProLiant (SPP) Bundled Software earlier than version 2018.09.0.
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 local access restriction bypass vulnerability in HPE Service Pack for ProLiant (SPP) Bundled Software versions prior to 2018.09.0. The vulnerability allows a local attacker to bypass intended access restrictions, potentially gaining unauthorized access to system resources or functionality that should be restricted.
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< 2018.09.0CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:L/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 the installed HPE Service Pack for ProLiant versionLocate the SPP version information on the system. This is typically displayed during the boot process, in the SPP welcome screen, or can be retrieved via the iLO web interface under the 'Overall Health' or 'System Information' section. Check any documentation or deployment records if the system was recently updated.Affected if The displayed version number is less than 2018.09.0 (for example, 2018.04.0, 2017.x, or earlier)
-
Verify the SPP version from the iLO interfaceLog into the iLO web interface using administrator credentials. Navigate to the 'Information' or 'Summary' page where the firmware bundle version is displayed. The SPP version is often listed as the 'Service Pack' or 'Firmware Bundle' version.Affected if The iLO-reported SPP version is a release prior to 2018.09.0
-
Confirm the local attack surface existsDetermine if the system allows local access by users without administrative privileges. Check if there are local user accounts, physical console access, or mechanisms that could allow a local attacker to interact with the system.Affected if Local users or processes with limited privileges exist on the system and the SPP version is below 2018.09.0
The environment is affected if HPE Service Pack for ProLiant is installed at a version prior to 2018.09.0 and the system is accessible to local attackers who could exploit the access restriction bypass.
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 data2018.09.0
Upgrade HPE Service Pack for ProLiant to version 2018.09.0 or later to remediate this vulnerability.
- Consultation3.0 h
- Implementation6.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-7118 — 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-7118 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