dbcve.org
3par Service ProviderOperating system · Hp

CVE-2018-7095

CRITICAL · 9.8 CVSS v3.0 Published 2018-08-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
A security vulnerability was identified in 3PAR Service Processor (SP) prior to SP-4.4.0.GA-110(MU7). The vulnerability may be exploited remotely to allow access restriction bypass.

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 confidence

A critical vulnerability in HPE 3PAR Service Processor allows remote attackers to bypass access restrictions. The flaw exists in versions prior to SP-4.4.0.GA-110(MU7), and the high CVSS score (9.8) indicates trivial network exploitation with complete compromise potential.

MitigationUpgrade the 3PAR Service Processor to version SP-4.4.0.GA-110(MU7) or later. Schedule maintenance window and ensure proper backup of SP configuration before applying the update.

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
3par Service ProviderOperating system
Affected:= sp-4.2.0= sp-4.3.0= sp-4.4.0

CVSS 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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify HPE 3PAR Service Processor presence
    Locate any HPE 3PAR Service Processor appliances or virtual machines in your environment. Check inventory systems, virtualization platforms, or physical server lists for SP deployments.
    Affected if HPE 3PAR Service Processor is present in the environment
  2. Determine Service Processor version
    Access the Service Processor management interface or console. Run the command to display the SP version, typically found in system information or via CLI command 'showversion' or similar.
    Affected if The displayed version matches sp-4.2.0, sp-4.3.0, or sp-4.4.0, or shows a build prior to SP-4.4.0.GA-110(MU7)
  3. Verify network accessibility of Service Processor
    Confirm the Service Processor has an active network interface and is reachable on the network. Check if ports or services are exposed that could allow remote access.
    Affected if The Service Processor is network-accessible and the vulnerability can be exploited remotely
  4. Confirm affected configuration
    Review SP configuration to determine if default or weak access controls are in place. The vulnerability allows bypassing access restrictions, so any SP with network-facing services is potentially exploitable.
    Affected if Network-accessible SP with any user-accessible services on versions prior to SP-4.4.0.GA-110(MU7)

You are affected if an HPE 3PAR Service Processor is deployed with version sp-4.2.0, sp-4.3.0, sp-4.4.0, or any build prior to SP-4.4.0.GA-110(MU7) and is network-accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade the 3PAR Service Processor to version SP-4.4.0.GA-110(MU7) or later. Schedule maintenance window and ensure proper backup of SP configuration before applying the update.

Recommended fix High confidence

SP-4.4.0.GA-110(MU7) or later

  1. Back up the current 3PAR Service Processor configuration according to HPE best practices
  2. Download SP-4.4.0.GA-110(MU7) or later from the HPE Support Center (support.hpe.com)
  3. Follow the HPE Service Processor update documentation to apply the upgrade
  4. Verify the upgrade completed successfully and the vulnerability is resolved

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in 3par Service Provider Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-7095 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-7095 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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