CVE-2020-5372
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 · uneditedDell EMC PowerStore versions prior to 1.0.1.0.5.002 contain a vulnerability that exposes test interface ports to external network. A remote unauthenticated attacker could potentially cause Denial of Service via test interface ports which are not used during run time environment.
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 confidenceDell EMC PowerStore versions prior to 1.0.1.0.5.002 expose test interface ports to external networks, allowing remote unauthenticated attackers to cause Denial of Service by accessing these non-production ports.
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< 1.0.1.0.5.002< 1.0.1.0.5.002< 1.0.1.0.5.002< 1.0.1.0.5.002< 1.0.1.0.5.002CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 PowerStore model and firmware versionAccess the PowerStore management interface (UEM or REST API) and retrieve the current firmware version. This is typically found in the system settings or hardware inventory section.Affected if The firmware version is lower than 1.0.1.0.5.002 on any of these models: PowerStore 1000, 3000, 5000, 7000, or 9000.
-
Locate test interface ports in network configurationReview the PowerStore network configuration to identify any test or diagnostic interface ports. These are typically non-production ports used during manufacturing or maintenance.Affected if Test interface ports are present and configured in the active network configuration.
-
Verify external network accessibility of test portsCheck firewall rules, access control lists, and network segmentation policies to determine whether the test interface ports are reachable from external or untrusted networks.Affected if Test interface ports are accessible from networks outside the trusted management or maintenance segment.
-
Confirm exposure to unauthenticated remote accessDetermine if the test interface ports allow remote unauthenticated access without requiring authentication credentials or VPN tunnel.Affected if The test ports accept connections from external hosts without authentication.
The system is affected if the PowerStore firmware version is below 1.0.1.0.5.002 AND test interface ports are exposed to external networks, allowing remote unauthenticated attackers to trigger denial of service.
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 data1.0.1.0.5.002
Upgrade PowerStore to version 1.0.1.0.5.002 or later, or implement network segmentation and firewall rules to block external access to test interface ports.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.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 $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-5372 — 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-2020-5372 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