CVE-2020-5386
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 ECS, versions prior to 3.5, contains an Exposure of Resource vulnerability. A remote unauthenticated attacker can access the list of DT (Directory Table) objects of all internally running services and gain knowledge of sensitive data of the system.
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 confidenceDell EMC ECS versions prior to 3.5 contain an information disclosure vulnerability where a remote unauthenticated attacker can access Directory Table (DT) objects that expose sensitive metadata about all internally running services on the storage system.
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< 3.5.0.0CVSS 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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 the installed ECS versionAccess the ECS management interface or use the administrative CLI to retrieve the current software version. Common methods include checking the About/Version page in the ECS management UI or running 'ecs-version' or 'cat /var/emc/version' via SSH if you have admin access.Affected if The installed version is any release prior to 3.5.0.0 (for example, 3.4.x, 3.3.x, or earlier)
-
Determine if the management network is exposedReview network firewall rules and ACLs to determine whether the ECS management interfaces (typically ports 443, 4443, or SSH) are reachable from untrusted networks or the public internet.Affected if The ECS management interface is accessible from networks outside the trusted administrative zone, since the vulnerability can be exploited remotely without authentication
-
Verify if the DT object endpoint is accessibleAttempt to reach the ECS API or management endpoint that exposes Directory Table objects. Since specific endpoint details were not provided, test access to common management URLs over HTTPS and observe whether the request returns service metadata without requiring credentials.Affected if The system responds to unauthenticated requests with metadata about internal services or DT objects, indicating the vulnerability is exposed
You are affected if your ECS version is below 3.5.0.0 AND the management interface is network-accessible to untrusted parties, allowing remote unauthenticated access to sensitive service metadata.
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 data3.5.0.0
Upgrade Dell EMC ECS to version 3.5 or later to remediate this vulnerability. As a network-exploitable issue requiring no authentication, restrict management network access until the upgrade is applied.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-5386 — 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-5386 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