CVE-2019-5399
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 gain authorized access vulnerability was discovered in HPE 3PAR Service Processor version(s): prior to 5.0.5.1.
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 confidenceHPE 3PAR Service Processor versions prior to 5.0.5.1 contain a critical vulnerability allowing remote attackers to gain unauthorized access. The CVSS 9.4 score indicates a network-exploitable flaw with low attack complexity and no authentication required.
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< 5.0.5.1CVSS 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
- Low
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 HPE 3PAR Service Processor installationLocate the Service Processor appliance in your infrastructure. This is typically a dedicated virtual or physical appliance connected to the 3PAR array for remote support and updates.Affected if The system is an HPE 3PAR Service Processor appliance
-
Determine Service Processor firmware versionAccess the Service Processor management interface via its web console or CLI. Run the command to display firmware version, typically 'showversion' or check the system information panel in the web UI.Affected if The installed firmware version is lower than 5.0.5.1
-
Confirm remote access feature is enabledVerify if the remote support connectivity feature (typically called 'Remote Service Processor' or 'Remote Support') is enabled on the 3PAR array. Check via the 3PAR CLI using 'showsps' or through the web interface under Support settings.Affected if Remote support/connectivity is enabled and the firmware version is below 5.0.5.1
You are affected if you have an HPE 3PAR Service Processor with firmware version lower than 5.0.5.1 and remote support connectivity is enabled.
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.
dbcve · scoped5.0.5.1
Upgrade HPE 3PAR Service Processor to version 5.0.5.1 or later to remediate this vulnerability.
5.0.5.1 or later
- Verify current HPE 3PAR Service Processor firmware version through the HPE management interface or CLI
- Download Service Processor firmware version 5.0.5.1 or later from support.hpe.com
- Schedule a maintenance window as firmware updates may require service downtime
- Follow HPE documentation for upgrading Service Processor firmware, typically via the SP management interface or CLI command interface
- Verify the upgrade was successful and the new firmware version is 5.0.5.1 or higher
- Confirm the vulnerability is resolved by checking the HPE security bulletin
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-5399 — 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-2019-5399 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