dbcve.org
Emc Idrac7Application · Dell

CVE-2018-1207

CRITICAL · 9.8 CVSS v3.0 Published 2018-03-23
Fix available
A fix is available. Upgrade to 2.52.52.52 or later.
See remediation →
100/100
Remediation priority · Urgent
High EPSS 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, versions prior to 2.52.52.52, contain CGI injection vulnerability which could be used to execute remote code. A remote unauthenticated attacker may potentially be able to use CGI variables to execute remote code.

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 iDRAC7 and iDRAC8 versions before 2.52.52.52 contain a CGI injection vulnerability that allows remote unauthenticated attackers to execute arbitrary code by manipulating CGI variables. This critical flaw affects the web-based remote management interface of these baseboard management controllers.

MitigationUpgrade iDRAC7/iDRAC8 firmware to version 2.52.52.52 or later to remediate the CGI injection vulnerability.

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
Emc Idrac7Application
Affected:< 2.52.52.52
Emc Idrac8Application
Affected:< 2.52.52.52

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. Check iDRAC firmware version via web interface
    Log into the iDRAC web interface (https://[ip-address]) and navigate to the Overview > iDRAC Settings > About page to view the firmware version
    Affected if Firmware version displayed is below 2.52.52.52
  2. Check iDRAC firmware version via racadm CLI
    Run the command 'racadm getversion' or 'racadm fwversion' from a system with racadm installed to query the iDRAC firmware version remotely
    Affected if The reported firmware version is less than 2.52.52.52
  3. Check iDRAC web server status
    Access iDRAC settings via web interface under iDRAC Settings > Services > Web Server, or run 'racadm get iDRAC.WebServer.1' to verify the web server is enabled
    Affected if Web server is enabled AND firmware version is below 2.52.52.52
  4. Confirm iDRAC model type
    Identify whether the managed device uses iDRAC7 or iDRAC8 by checking the model in the web interface Overview page or via 'racadm get System.Info.1'
    Affected if Model is iDRAC7 or iDRAC8 AND version is below 2.52.52.52

The environment is affected if the iDRAC7 or iDRAC8 firmware version is below 2.52.52.52 and the web-based management interface is enabled.

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.52.52.52 or later
Fixed in 2.52.52.52
Interim mitigation

Upgrade iDRAC7/iDRAC8 firmware to version 2.52.52.52 or later to remediate the CGI injection vulnerability.

Recommended fix High confidence

iDRAC7/iDRAC8 firmware version 2.52.52.52 or later

  1. 1. Download the iDRAC firmware version 2.52.52.52 or later from Dell's official support website (support.dell.com)
  2. 2. Log into the iDRAC web interface as an administrator
  3. 3. Navigate to iDRAC Settings > Maintenance > System Update > Manual Update
  4. 4. Click 'Upload' and select the downloaded firmware update file (.exe or .bin format)
  5. 5. Click 'Install' to stage the firmware for update
  6. 6. Wait for the firmware upload to complete, then click 'Apply' to apply the update
  7. 7. Allow the iDRAC to reboot automatically - this may take several minutes
  8. 8. After reboot, verify the new version by checking iDRAC Settings > About iDRAC
Caveat Firmware update requires iDRAC reboot causing temporary loss of remote management connectivity; ensure planned maintenance window and backup of iDRAC configuration

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

Fix this in Emc Idrac7 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 the upgrade done

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-2018-1207 — 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-2018-1207 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