CVE-2018-7094
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 was identified in 3PAR Service Processor (SP) prior to SP-5.0.0.0-22913(GA). The vulnerability may be exploited locally to allow disclosure of privileged 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 local vulnerability in 3PAR Service Processor versions prior to SP-5.0.0.0-22913 allows an attacker with local access to disclose privileged information. The attack vector is local (AV:L), requires low privileges, and results in confidentiality impact without affecting integrity or availability.
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< sp-5.0.0.0-22913CVSS 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
- None
- Availability
- None
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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 HPE 3PAR Service Processor deploymentLocate the Service Processor system in your environment - this is a separate management appliance that manages HPE 3PAR storage arrays. Check your inventory or network documentation for 3PAR SP systems.Affected if A 3PAR Service Processor exists in your environment
-
Determine the installed Service Processor versionAccess the SP command line or management interface and retrieve the firmware/software version. Common methods include running 'version' or 'showversion' commands via SSH to the SP, or checking via HPE 3PAR management tools.Affected if The version returned is less than SP-5.0.0.0-22913
-
Compare against vulnerable version rangeReview the version number obtained from the SP. The affected range is any version lower than SP-5.0.0.0-22913.Affected if Installed version starts with sp- followed by a number less than 5.0.0.0, or is 5.0.0.0.xxxxx where xxxxx is less than 22913
-
Verify local access attack vector applicabilityConfirm whether untrusted local users or processes have access to the Service Processor system. This vulnerability requires local access (AV:L) to exploit.Affected if Local users with low privileges can access the SP system
You are affected if an HPE 3PAR Service Processor in your environment runs a version lower than SP-5.0.0.0-22913 and local untrusted users can access that system.
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 dataUpgrade the 3PAR Service Processor to version SP-5.0.0.0-22913(GA) or later. Coordinate the update during a maintenance window as the SP is a critical component for storage array management.
- Consultation4.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,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-7094 — 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-7094 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