CVE-2020-5366
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 iDRAC9 versions prior to 4.20.20.20 contain a Path Traversal Vulnerability. A remote authenticated malicious user with low privileges could potentially exploit this vulnerability by manipulating input parameters to gain unauthorized read access to the arbitrary files.
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 iDRAC9 versions prior to 4.20.20.20 contain a path traversal vulnerability. A remote authenticated attacker with low-privilege credentials can manipulate input parameters to read arbitrary files on the system, potentially exposing sensitive configuration data or credentials.
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.20.20.20CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Confirm iDRAC9 is presentAccess the iDRAC web interface or use racadm command line tool (racadm get iDRAC.Info) to identify the device. Look for iDRAC9 in the system information.Affected if The managed system is running Dell iDRAC9 firmware.
-
Check installed firmware versionUse racadm command: racadm get iDRAC.FirmwareInfo or view the iDRAC web interface under iDRAC Settings > Firmware. Compare the firmware version to 4.20.20.20.Affected if The installed firmware version is less than 4.20.20.20.
-
Verify remote management access is enabledCheck iDRAC network settings via web interface (iDRAC Settings > Network) or command: racadm get iDRAC.WebServer.1.IPv4Enabled or racadm get iDRAC.RemoteHosts.Confirm that remote access (web server, SSH, or Redfish API) is enabled.Affected if iDRAC remote management interfaces are accessible from network.
-
Identify configured iDRAC user accountsList iDRAC users via racadm get iDRAC.Users or view Users page in web interface. Check for any user accounts with limited privileges (non-Administrator).Affected if There are any authenticated user accounts configured in iDRAC, even with low-level privileges.
If iDRAC9 is in use with firmware version below 4.20.20.20, remote management enabled, and any user accounts exist, the system is potentially vulnerable to authenticated path traversal attacks.
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 data4.20.20.20
Update iDRAC9 firmware to version 4.20.20.20 or later to remediate the path traversal vulnerability.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-5366 — 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-5366 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