Emc PowermaxApplication · Dell

CVE-2019-18588

MEDIUM · 5.4 CVSS v3.1 Published 2020-01-10
Fix available
A fix is available. Upgrade to 9.0.2.16 / 9.1.0.9 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
Dell EMC Unisphere for PowerMax versions prior to 9.1.0.9, Dell EMC Unisphere for PowerMax versions prior to 9.0.2.16, and Dell EMC PowerMax OS 5978.221.221 and 5978.479.479 contain a Cross-Site Scripting (XSS) vulnerability. An authenticated malicious user may potentially exploit this vulnerability to inject javascript code and affect other authenticated users' sessions.

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 confidence

A stored Cross-Site Scripting (XSS) vulnerability in Dell EMC Unisphere for PowerMax allows authenticated malicious users to inject arbitrary JavaScript code that executes in the browsers of other authenticated users, enabling session hijacking or credential theft.

MitigationUpgrade Unisphere for PowerMax to version 9.1.0.9 or 9.0.2.16 or later, and apply vendor patches for PowerMax OS versions 5978.221.221 and 5978.479.479 to remediate the XSS vulnerability.

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
Emc PowermaxApplication
Affected:= 5978.221.221= 5978.479.479
Emc Unisphere For PowermaxApplication
Affected:< 9.0.2.16>= 9.1.0.0, < 9.1.0.9

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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/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 checks

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

  1. Confirm Unisphere for PowerMax is running
    Access the Unisphere web interface URL or check for the Unisphere application service in your system inventory. This vulnerability affects the Unisphere web application specifically.
    Affected if Unisphere for PowerMax is accessible via web interface and you are using it to manage a PowerMax array
  2. Identify the Unisphere for PowerMax version
    Log into the Unisphere web interface and navigate to the About or System Information section, typically found under Settings or Help. Alternatively, use the Unisphere command-line interface if available to query the version.
    Affected if The installed version is 9.0.x below 9.0.2.16, or 9.1.0.0 through 9.1.0.8
  3. Identify the PowerMax OS version
    Access the PowerMax storage array via its management interface (such as Solutions Enabler or the embedded Unisphere) and query the array OS version. This is typically displayed in the array status or system information panel.
    Affected if The PowerMax OS version is exactly 5978.221.221 or exactly 5978.479.479
  4. Verify XSS is exploitable in your environment
    Confirm that multiple authenticated users access the Unisphere web interface. A stored XSS only affects environments where multiple users view the same data fields where malicious code could be injected.
    Affected if Multiple authenticated users share access to Unisphere and can view each others data or configuration entries

You are affected if Unisphere for PowerMax version is below 9.0.2.16 (for 9.0.x) or between 9.1.0.0 and 9.1.0.8, OR if the PowerMax OS is exactly 5978.221.221 or 5978.479.479, and multiple users access the Unisphere interface.

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.

From vendor data
Upgrade available Upgrade to 9.0.2.16 / 9.1.0.9 or later
Fixed in 9.0.2.169.1.0.9
Interim mitigation

Upgrade Unisphere for PowerMax to version 9.1.0.9 or 9.0.2.16 or later, and apply vendor patches for PowerMax OS versions 5978.221.221 and 5978.479.479 to remediate the XSS vulnerability.

Fix this in Emc Powermax 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 the upgrade done

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-2019-18588 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-18588 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