Emc Unisphere For PowermaxApplication · Dell

CVE-2020-5367

HIGH · 8.1 CVSS v3.1 Published 2020-06-23
Fix available
A fix is available. Upgrade to 9.1.0.17 or later.
See remediation →
90/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
Dell EMC Unisphere for PowerMax versions prior to 9.1.0.17, Dell EMC Unisphere for PowerMax Virtual Appliance versions prior to 9.1.0.17, and PowerMax OS Release 5978 contain an improper certificate validation vulnerability. An unauthenticated remote attacker may potentially exploit this vulnerability to carry out a man-in-the-middle attack by supplying a crafted certificate and intercepting the victim's traffic to view or modify a victim's data in transit.

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

Dell EMC Unisphere for PowerMax and PowerMax OS contain an improper certificate validation vulnerability where the system fails to properly verify SSL/TLS certificates during secure connections. This allows an unauthenticated remote attacker to perform a man-in-the-middle attack by presenting a crafted certificate, enabling interception and modification of data in transit.

MitigationUpgrade Unisphere for PowerMax and Unisphere for PowerMax Virtual Appliance to version 9.1.0.17 or later, and apply the fix for PowerMax OS Release 5978 to address the certificate validation weakness.

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 Unisphere For PowermaxApplication
Affected:< 9.1.0.17
Emc Unisphere For Powermax Virtual ApplianceApplication
Affected:< 9.1.0.17
Powermax OsOperating system
Affected:= 5978

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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/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 Unisphere for PowerMax version
    Access the Unisphere web interface or use the 'unisphere -version' CLI command to determine the installed version of Unisphere for PowerMax
    Affected if Version is less than 9.1.0.17
  2. Identify Unisphere for PowerMax Virtual Appliance version
    Check the virtual appliance version through the vSphere client or by running 'get system info' from the appliance CLI
    Affected if Version is less than 9.1.0.17
  3. Identify PowerMax OS version
    Run the 'sysctl -a' command or check the PowerMax management interface to retrieve the PowerMax OS release version
    Affected if PowerMax OS version equals 5978 exactly
  4. Verify SSL/TLS is enabled for Unisphere
    Check the Unisphere configuration settings or inspect the SSL/TLS service status via the Unisphere admin console under Security or Network settings
    Affected if SSL/TLS is enabled and the version check shows an affected version in steps 1-3
  5. Inspect SSL certificate validation configuration
    Review the Unisphere configuration files or management interface for SSL certificate validation settings to confirm whether custom certificates or certificate chain validation is properly configured
    Affected if Certificate validation is set to allow unverified or self-signed certificates without proper chain verification

A user is affected if they are running Unisphere for PowerMax or PowerMax Virtual Appliance versions below 9.1.0.17, or PowerMax OS version 5978, with SSL/TLS enabled and weak certificate validation configured.

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.1.0.17 or later
Fixed in 9.1.0.17
Interim mitigation

Upgrade Unisphere for PowerMax and Unisphere for PowerMax Virtual Appliance to version 9.1.0.17 or later, and apply the fix for PowerMax OS Release 5978 to address the certificate validation weakness.

Fix this in Emc Unisphere For Powermax Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-5367 — 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-2020-5367 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