CVE-2019-5398
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 multiple multiple cross-site 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 cross-site scripting (XSS) vulnerability in HPE 3PAR Service Processor allows attackers to inject malicious scripts via unspecified vectors. The vulnerability affects versions prior to 5.0.5.1 and is exploitable over the network without authentication, potentially allowing session hijacking or credential theft.
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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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 deploymentDetermine if HPE 3PAR Service Processor is present in your environment by reviewing hardware inventory or consulting with infrastructure teamsAffected if HPE 3PAR Service Processor is not deployed, the system is not affected by this CVE
-
Determine Service Processor firmware versionAccess the Service Processor management interface or use the command 'showsp' via the 3PAR CLI to retrieve the installed firmware versionAffected if The displayed version is a release earlier than 5.0.5.1 (for example, 5.0.0.0, 5.0.1.0, 5.0.4.0)
-
Compare version against affected rangeCompare the installed firmware version number to the affected range: any version less than 5.0.5.1 is vulnerableAffected if The firmware version is below 5.0.5.1, indicating the system is affected by this vulnerability
-
Verify network accessibility of Service ProcessorDetermine if the Service Processor web interface is reachable over the network from untrusted segmentsAffected if The Service Processor is network-accessible without authentication and the firmware version is below 5.0.5.1
A system is affected if HPE 3PAR Service Processor firmware version is below 5.0.5.1 and the management interface is 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.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-5398 — 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-5398 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