dbcve.org
Idrac6 FirmwareOperating system · Dell

CVE-2019-3705

CRITICAL · 9.8 CVSS v3.1 Published 2019-04-26
Fix available
A fix is available. Upgrade to 2.61.60.60 / 2.92 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 iDRAC6 versions prior to 2.92, iDRAC7/iDRAC8 versions prior to 2.61.60.60, and iDRAC9 versions prior to 3.20.21.20, 3.21.24.22, 3.21.26.22 and 3.23.23.23 contain a stack-based buffer overflow vulnerability. An unauthenticated remote attacker may potentially exploit this vulnerability to crash the webserver or execute arbitrary code on the system with privileges of the webserver by sending specially crafted input data to the affected 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 · high confidence

Stack-based buffer overflow vulnerability in Dell EMC iDRAC web interface allows unauthenticated remote attackers to send specially crafted input that overflows a stack buffer, potentially executing arbitrary code with webserver privileges or causing denial of service.

MitigationApply vendor patches (iDRAC6: 2.92+, iDRAC7/8: 2.61.60.60+, iDRAC9: 3.20.21.20+/3.21.24.22+/3.21.26.22+/3.23.23.23+). If immediate patching is not feasible, restrict network access to the iDRAC management interface to reduce attack surface.

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
Idrac6 FirmwareOperating system
Affected:< 2.92
Idrac7 FirmwareOperating system
Affected:< 2.61.60.60
Idrac8 FirmwareOperating system
Affected:< 2.61.60.60
Idrac9 FirmwareOperating system
Affected:< 3.20.21.20

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 iDRAC firmware version via web interface
    Log into the iDRAC web interface and navigate to the 'About' or 'Firmware Version' page in the iDRAC Settings. The firmware version is displayed there.
    Affected if The displayed firmware version is below 2.92 for iDRAC6, below 2.61.60.60 for iDRAC7/8, or below 3.20.21.20 for iDRAC9.
  2. Identify iDRAC firmware version via RACADM CLI
    Run the command 'racadm getversion' or 'racadm get idrac.FirmwareInfo' from a system with RACADM installed and network access to the iDRAC IP address.
    Affected if The FirmwareVersion field shows a version below 2.92 for iDRAC6, below 2.61.60.60 for iDRAC7/8, or below 3.20.21.20 for iDRAC9.
  3. Identify iDRAC firmware version via Redfish API
    Send a GET request to https://<idrac-ip>/redfish/v1/Managers/iDRAC.Embedded.1/ and examine the 'FirmwareVersion' field in the JSON response.
    Affected if The 'FirmwareVersion' value is below 2.92 for iDRAC6, below 2.61.60.60 for iDRAC7/8, or below 3.20.21.20 for iDRAC9.
  4. Identify iDRAC firmware version via IPMI
    Run the command 'ipmitool -I lanplus -H <idrac-ip> -U root -P password raw' with appropriate credentials, or use 'ipmitool mc info' to retrieve firmware information.
    Affected if The firmware revision shown is numerically lower than the affected version thresholds for your iDRAC generation.

You are affected if your iDRAC firmware version falls below the minimum fixed version for your specific iDRAC model (6, 7, 8, or 9).

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.61.60.60 / 2.92 / 3.20.21.20 or later
Fixed in 2.61.60.602.923.20.21.20
Interim mitigation

Apply vendor patches (iDRAC6: 2.92+, iDRAC7/8: 2.61.60.60+, iDRAC9: 3.20.21.20+/3.21.24.22+/3.21.26.22+/3.23.23.23+). If immediate patching is not feasible, restrict network access to the iDRAC management interface to reduce attack surface.

Recommended fix High confidence

iDRAC6: >=2.92 | iDRAC7: >=2.61.60.60 | iDRAC8: >=2.61.60.60 | iDRAC9: >=3.20.21.20 (or 3.21.24.22/3.21.26.22/3.23.23.23)

  1. 1. Identify the current iDRAC firmware version by accessing the iDRAC web interface or using racadm command: racadm get iDRAC.FirmwareInfo
  2. 2. Determine the appropriate iDRAC model (6, 7, 8, or 9) from your Dell server
  3. 3. Download the firmware update package from Dell's support site (www.dell.com) matching your iDRAC model
  4. 4. For iDRAC6: Upgrade to firmware version 2.92 or later
  5. 5. For iDRAC7: Upgrade to firmware version 2.61.60.60 or later
  6. 6. For iDRAC8: Upgrade to firmware version 2.61.60.60 or later
  7. 7. For iDRAC9: Upgrade to firmware version 3.20.21.20, 3.21.24.22, 3.21.26.22, or 3.23.23.23 or later
  8. 8. Apply the firmware update via iDRAC web interface, racadm, or Dell Update Package (DUP) following Dell's documented upgrade procedure
Caveat Firmware updates may require server downtime and should be tested in a non-production environment first; ensure backup of iDRAC configuration before upgrade

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

Fix this in Idrac6 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
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,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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