dbcve.org
Idrac9 FirmwareOperating system · Dell

CVE-2019-3706

CRITICAL · 9.8 CVSS v3.0 Published 2019-04-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 iDRAC9 versions prior to 3.24.24.24, 3.21.26.22, 3.22.22.22 and 3.21.25.22 contain an authentication bypass vulnerability. A remote attacker may potentially exploit this vulnerability to bypass authentication and gain access to the system by sending specially crafted data to the iDRAC web interface.

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

Dell EMC iDRAC9 versions prior to 3.24.24.24, 3.21.26.22, 3.22.22.22 and 3.21.25.22 contain an authentication bypass vulnerability in the iDRAC web interface. A remote unauthenticated attacker can exploit this by sending specially crafted data to bypass authentication and gain administrative access to the remote management controller, potentially controlling the entire host server.

MitigationUpgrade iDRAC9 firmware to version 3.24.24.24, 3.21.26.22, 3.22.22.22, 3.21.25.22 or later. If patching is not immediately possible, restrict network access to the iDRAC management interface using firewall rules or VLAN segmentation to limit exposure.

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
Idrac9 FirmwareOperating system
Affected:= 3.20.21.20= 3.21.24.22= 3.23.23.23

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.0/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. Confirm iDRAC9 is present
    Access the iDRAC web interface via browser or use 'racadm get iDRAC.Info' command-line tool to verify the device is an iDRAC9
    Affected if System is not an iDRAC9 controller
  2. Retrieve iDRAC firmware version
    In the iDRAC web interface, navigate to Overview > iDRAC Settings > Summary page, or run 'racadm get iDRAC.FirmwareInfo' to display the current firmware version
    Affected if Unable to retrieve version information
  3. Compare installed version to affected ranges
    Compare your firmware version (e.g., 3.20.21.20, 3.21.24.22, 3.23.23.23) against the vulnerable versions: any version prior to 3.24.24.24, 3.21.26.22, 3.22.22.22, or 3.21.25.22
    Affected if Installed version is lower than the fixed versions listed (3.24.24.24, 3.21.26.22, 3.22.22.22, or 3.21.25.22)
  4. Check if web interface is network-accessible
    Verify the iDRAC web interface (port 443) is reachable from network segments outside the management VLAN, or run a port scan against the iDRAC IP on port 443
    Affected if Web interface is exposed to untrusted networks without firewall protection

The environment is affected if iDRAC9 firmware version is 3.20.21.20, 3.21.24.22, 3.23.23.23 or any version prior to the fixed releases (3.24.24.24, 3.21.26.22, 3.22.22.22, or 3.21.25.22) and the web interface is network-accessible.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade iDRAC9 firmware to version 3.24.24.24, 3.21.26.22, 3.22.22.22, 3.21.25.22 or later. If patching is not immediately possible, restrict network access to the iDRAC management interface using firewall rules or VLAN segmentation to limit exposure.

Recommended fix High confidence

iDRAC9 firmware version 3.24.24.24 or later (or at minimum 3.21.26.22, 3.22.22.22, or 3.21.25.22 depending on your baseline)

  1. 1. Download the iDRAC9 firmware update (version 3.24.24.24 or later) from Dell's support website (www.dell.com/support)
  2. 2. Log into the iDRAC web interface as an administrator
  3. 3. Navigate to Maintenance > System Update > Firmware Update
  4. 4. Upload the downloaded firmware update file
  5. 5. Apply the firmware update and wait for the iDRAC to reboot
  6. 6. Verify the firmware version has been updated by checking iDRAC Settings > About in the web interface
Caveat Firmware update may cause brief iDRAC service interruption during the update process; ensure proper power and network connectivity throughout the update

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

Fix this in Idrac9 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-3706 — 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-2019-3706 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