dbcve.org
Idrac7 FirmwareOperating system · Dell

CVE-2020-5344

CRITICAL · 9.8 CVSS v3.1 Published 2020-03-31
Fix available
A fix is available. Upgrade to 2.65.65.65 / 2.70.70.70 or later.
See remediation →
100/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 iDRAC7, iDRAC8 and iDRAC9 versions prior to 2.65.65.65, 2.70.70.70, 4.00.00.00 contain a stack-based buffer overflow vulnerability. An unauthenticated remote attacker may exploit this vulnerability to crash the affected process or execute arbitrary code on the system by sending specially crafted input data.

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

A stack-based buffer overflow vulnerability exists in Dell EMC iDRAC7, iDRAC8, and iDRAC9 firmware versions prior to 2.65.65.65, 2.70.70.70, and 4.00.00.00 respectively. An unauthenticated remote attacker can send specially crafted input data to overflow a stack buffer, potentially crashing the affected process or achieving arbitrary code execution with the privileges of the affected service.

MitigationUpdate iDRAC firmware to version 2.65.65.65 or later for iDRAC7, 2.70.70.70 or later for iDRAC8, and 4.00.00.00 or later for iDRAC9. Restrict network access to iDRAC management interfaces to trusted networks until patching is complete.

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
Idrac7 FirmwareOperating system
Affected:< 2.65.65.65
Idrac8 FirmwareOperating system
Affected:< 2.70.70.70
Idrac9 FirmwareOperating system
Affected:< 4.00.00.00

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

CVSS:3.1/AV:N/AC:L/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 the iDRAC model
    Access the iDRAC web interface or use racadm get iDRAC.Info command or IPMI command ipmitool -I lanplus -H <idrac-ip> -U root -P <password> raw command to determine if the device uses iDRAC7, iDRAC8, or iDRAC9 firmware
    Affected if The model is iDRAC7, iDRAC8, or iDRAC9 and the firmware version is below the fixed versions
  2. Retrieve the installed firmware version
    Via iDRAC Web UI: navigate to Overview > iDRAC Settings > Firmware. Via RACADM: run racadm get firmware. Via Redfish: GET /redfish/v1/Managers/iDRAC.Embedded.1/FirmwareInventory
    Affected if Unable to retrieve version or version is displayed as an older release
  3. Compare version against affected ranges
    For iDRAC7: check if version < 2.65.65.65. For iDRAC8: check if version < 2.70.70.70. For iDRAC9: check if version < 4.00.00.00
    Affected if The installed version falls below the corresponding threshold for the detected model
  4. Verify iDRAC network accessibility
    Confirm whether the iDRAC management interface (typically ports 443, 623 UDP) is reachable from untrusted networks using nmap -p 443,623 <idrac-ip> or similar network scanning
    Affected if iDRAC is exposed to untrusted networks and the firmware version is confirmed vulnerable

If the iDRAC model is 7, 8, or 9 and the firmware version is below 2.65.65.65, 2.70.70.70, or 4.00.00.00 respectively, the environment is affected by this vulnerability.

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.

dbcve · scoped
Upgrade available Upgrade to 2.65.65.65 / 2.70.70.70 / 4.00.00.00 or later
Fixed in 2.65.65.652.70.70.704.00.00.00
Interim mitigation

Update iDRAC firmware to version 2.65.65.65 or later for iDRAC7, 2.70.70.70 or later for iDRAC8, and 4.00.00.00 or later for iDRAC9. Restrict network access to iDRAC management interfaces to trusted networks until patching is complete.

Recommended fix High confidence

iDRAC7: upgrade to firmware 2.65.65.65 or later | iDRAC8: upgrade to firmware 2.70.70.70 or later | iDRAC9: upgrade to firmware 4.00.00.00 or later

  1. 1. Identify the iDRAC model (iDRAC7, iDRAC8, or iDRAC9) by accessing the iDRAC web interface or checking the Dell system BIOS.
  2. 2. Determine the current iDRAC firmware version through the web interface under 'iDRAC Settings > Overview > Firmware' or via racadm command: racadm get iDRAC.FirmwareInfo
  3. 3. Navigate to Dell Support (www.dell.com) and search for the specific iDRAC firmware for your server model.
  4. 4. Download the firmware update package: for iDRAC7 use version 2.65.65.65 or later; for iDRAC8 use version 2.70.70.70 or later; for iDRAC9 use version 4.00.00.00 or later.
  5. 5. Apply the firmware update via the iDRAC web interface (under 'iDRAC Settings > Firmware Update') or via racadm: racadm fwupdate -f <firmware_file> -u admin -p <password>
  6. 6. Wait for the firmware update to complete and for iDRAC to reboot.
  7. 7. Verify the firmware version has been updated to the secure version by checking 'iDRAC Settings > Overview > Firmware' or using racadm.
Caveat Firmware updates carry inherent risk of system interruption; ensure proper backups and maintenance window; verify compatibility with connected systems before applying

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Idrac7 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-5344 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-5344 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