CVE-2020-5368
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 VxRail versions 4.7.410 and 4.7.411 contain an improper authentication vulnerability. A remote unauthenticated attacker may exploit this vulnerability to obtain sensitive information in an encrypted form.
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 VxRail versions 4.7.410 and 4.7.411 contain an improper authentication vulnerability that allows remote unauthenticated attackers to bypass authentication mechanisms and obtain sensitive information stored in encrypted form.
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= 4.7.410= 4.7.411= 4.7.510= 4.7.410= 4.7.411= 4.7.510CVSS 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 VxRail firmware versionAccess the VxRail Manager UI or use the command 'vxrail-cli -t get-version' to retrieve the installed firmware version. Alternatively, check via the vCenter plugin or REST API endpoint /v1/cluster/version.Affected if Version is 4.7.410, 4.7.411, or 4.7.510 on a D560 or D560f model.
-
Confirm VxRail model typeFrom the VxRail Manager UI under Settings > System > Hardware, or via the REST API /v1/nodes, verify the model is either D560 or D560f.Affected if Model is D560 or D560f AND firmware version is in the affected list.
-
Verify management network exposureCheck if the VxRail Manager management interface (typically ports 443, 22) is accessible from untrusted networks. Review firewall rules and network segments. Use 'show network' from VxRail CLI or check vCenter networking configuration.Affected if Management interface is exposed to networks outside the trusted administrative zone.
-
Check authentication configuration statusReview authentication settings in VxRail Manager under Security > Authentication Services. Confirm whether local accounts, LDAP, or other auth mechanisms are enabled and properly configured.Affected if Authentication is configured and the vulnerable firmware versions (4.7.410, 4.7.411, 4.7.510) are running.
A user is affected if they are running VxRail D560 or D560f firmware versions 4.7.410, 4.7.411, or 4.7.510 with management interfaces network-accessible to untrusted actors.
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 dataApply the vendor-supplied patch or upgrade to a fixed version beyond 4.7.411 when released by Dell EMC. As a Hyper-Converged Infrastructure appliance, patching should follow Dell's documented update procedures.
- Consultation4.0 h
- Implementation6.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 $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-5368 — 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-5368 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