CVE-2019-5395
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 arbitrary file upload 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 confidenceA remote arbitrary file upload vulnerability in HPE 3PAR Service Processor allows unauthenticated remote attackers to upload arbitrary files to the affected system, potentially leading to remote code execution. The vulnerability affects versions prior to 5.0.5.1.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/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 HPE 3PAR Service Processor in your environmentLocate systems running HPE 3PAR Service Processor firmware. This is typically a dedicated service processor appliance connected to 3PAR storage arrays.Affected if System is not an HPE 3PAR Service Processor, then this CVE does not apply.
-
Determine the installed Service Processor firmware versionAccess the Service Processor management interface or CLI and retrieve the firmware version information. Common methods include the 3PAR management console, SSH access to the Service Processor, or checking system information via the management GUI.Affected if Unable to determine the firmware version, cannot assess vulnerability status.
-
Compare your version against the vulnerable rangeCheck if the installed firmware version is any version prior to 5.0.5.1. Note that versions like 5.0.0.0, 5.0.1.0, 5.0.3.0, 5.0.4.0 and similar releases before 5.0.5.1 are all affected.Affected if Installed version is less than 5.0.5.1, the system is vulnerable to CVE-2019-5395.
-
Verify the remote management interface is accessibleCheck if the Service Processor remote management interface (typically exposed via network) is reachable from untrusted networks. The vulnerability allows unauthenticated file upload, so exposure to the network is the attack vector.Affected if Service Processor is directly exposed to the internet or untrusted networks without proper access controls, exploitation risk is higher.
You are affected if your HPE 3PAR Service Processor runs firmware version lower than 5.0.5.1 and has its management interface network-accessible.
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 data5.0.5.1
Upgrade HPE 3PAR Service Processor to version 5.0.5.1 or later to remediate this vulnerability.
- Consultation2.0 h
- Implementation4.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 $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-5395 — 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-5395 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