dbcve.org
Idrac6 BmcHardware / appliance · Dell

CVE-2013-4783

HIGH · 10.0 CVSS v2.0 Published 2013-07-08
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
The Dell iDRAC6 with firmware 1.x before 1.92 and 2.x and 3.x before 3.42, and iDRAC7 with firmware before 1.23.23, allows remote attackers to bypass authentication and execute arbitrary IPMI commands by using cipher suite 0 (aka cipher zero) and an arbitrary password. NOTE: the vendor disputes the significance of this issue, stating "DRAC's are intended to be on a separate management network; they are not designed nor intended to be placed on or connected to the Internet."

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 iDRAC6 and iDRAC7 firmware versions before 1.92/3.42 and 1.23.23 respectively contain an IPMI authentication bypass vulnerability. Attackers can use cipher suite 0 (cipher zero) with an arbitrary password to bypass authentication and execute arbitrary IPMI commands on the baseboard management controller, potentially achieving remote code execution at the firmware/hardware level.

MitigationApply vendor firmware updates (iDRAC6: 1.92/3.42+, iDRAC7: 1.23.23+) and ensure iDRAC interfaces are isolated on a dedicated management network not accessible from untrusted networks, as the vendor specifies.

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 BmcHardware / appliance
Affected:all versions

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
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

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 model
    Check the system for Dell iDRAC6 or iDRAC7 BMC by reviewing hardware documentation, BIOS boot logs, or accessing the iDRAC web interface. Look for iDRAC6 or iDRAC7 in the product name or service tag information.
    Affected if The system has an iDRAC6 or iDRAC7 baseboard management controller installed.
  2. Check iDRAC6 firmware version
    Access the iDRAC6 web interface and navigate to the Firmware Update or Overview section to view the current firmware version. Alternatively, use the racadm command: racadm getversion or check the firmware file if an update package exists.
    Affected if The installed firmware version is below 1.92 (for iDRAC6 1.x) or below 3.42 (for iDRAC6 3.x).
  3. Check iDRAC7 firmware version
    Access the iDRAC7 web interface and navigate to the Firmware Update or Overview section to view the current firmware version. Alternatively, use the racadm command: racadm getversion.
    Affected if The installed firmware version is below 1.23.23.
  4. Verify IPMI over LAN is enabled
    Check if IPMI over LAN is enabled on the BMC. Use the ipmitool command: ipmitool -I lanplus -H <idrac_ip> -U <user> channel info 1, or check via the iDRAC web interface under IPMI Settings or Network Settings.
    Affected if IPMI over LAN (IPMI over LAN access) is enabled, allowing remote IPMI commands to be sent to the BMC.
  5. Confirm cipher suite 0 is available
    Check the IPMI cipher suite configuration. Use ipmitool -I lanplus -H <idrac_ip> -U <user> lan print to view authentication options, or check the iDRAC web interface for IPMI security settings. Cipher suite 0 (cipher zero) must be available for the vulnerability to be exploitable.
    Affected if Cipher suite 0 is enabled or available in the IPMI configuration, allowing the bypass attack to succeed.

The system is affected if it runs a Dell iDRAC6 (any version) or iDRAC7 (below 1.23.23) with IPMI over LAN enabled and cipher suite 0 available for remote exploitation.

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

Apply vendor firmware updates (iDRAC6: 1.92/3.42+, iDRAC7: 1.23.23+) and ensure iDRAC interfaces are isolated on a dedicated management network not accessible from untrusted networks, as the vendor specifies.

Recommended fix Moderate confidence

iDRAC6: firmware 1.92+ (1.x branch) or 3.42+ (3.x branch); iDRAC7: firmware 1.23.23+

  1. 1. Identify the current iDRAC firmware version by accessing the iDRAC web interface or using racadm command: `racadm getversion`
  2. 2. For iDRAC6: upgrade to firmware version 1.92 or later for 1.x branch, or version 3.42 or later for 3.x branch
  3. 3. For iDRAC7: upgrade to firmware version 1.23.23 or later
  4. 4. Download firmware from Dell support website (support.dell.com) using your service tag
  5. 5. Upload and apply firmware via iDRAC web interface under Maintenance > Firmware Update, or via racadm: `racadm update -f <firmware_file>`
  6. 6. After update, verify the new firmware version is installed
  7. 7. Implement network isolation: place iDRAC on a dedicated management network VLAN, separate from production traffic
  8. 8. If network isolation is not possible, restrict access via firewall rules limiting iDRAC management to specific admin IP addresses only
Caveat Firmware updates may require iDRAC reset and brief service interruption; ensure out-of-band access is available before updating

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

Fix this in Idrac6 Bmc Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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