Idrac6 ModularApplication · Dell

CVE-2018-1212

HIGH · 8.8 CVSS v3.0 Published 2018-07-02
Fix available
A fix is available. Upgrade to 2.91 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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 web-based diagnostics console in Dell EMC iDRAC6 (Monolithic versions prior to 2.91 and Modular all versions) contains a command injection vulnerability. A remote authenticated malicious iDRAC user with access to the diagnostics console could potentially exploit this vulnerability to execute arbitrary commands as root on the affected iDRAC 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

A command injection vulnerability exists in the web-based diagnostics console of Dell EMC iDRAC6. A remote authenticated user with diagnostics console access can inject arbitrary OS commands through unsanitized input, executing them with root privileges on the iDRAC system.

MitigationUpdate iDRAC6 firmware to version 2.91 or later (monolithic); apply vendor patches for modular versions. Restrict diagnostics console access to essential personnel only 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
Idrac6 ModularApplication
Affected:all versions
Idrac6 MonolithicApplication
Affected:< 2.91

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

CVSS:3.0/AV:N/AC:L/PR:L/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 iDRAC6 model type
    Access the iDRAC web interface and check the device model under Overview > iDRAC Settings > Info, or use RACADM: racadm get iDRAC.Info. Look for 'Modular' or 'Monolithic' in the system model description.
    Affected if The system is a Dell iDRAC6 Modular (all versions affected) or iDRAC6 Monolithic (proceed to version check).
  2. Check iDRAC6 Monolithic firmware version
    If the model is Monolithic, check the firmware version via the web UI under Overview > iDRAC Settings > Info > Firmware Version, or via RACADM: racadm get iDRAC.Info.FirmwareVersion.
    Affected if The firmware version is below 2.91 (for example, 2.60, 2.80, etc.).
  3. Verify web-based diagnostics console is enabled
    Check if the diagnostics console functionality is accessible in the iDRAC web interface, typically under iDRAC Settings > Services or a dedicated Diagnostics section. Alternatively, attempt to access the diagnostics endpoint via browser if the URL pattern is known within your environment.
    Affected if The web-based diagnostics console is enabled and accessible via the iDRAC web interface.
  4. Confirm authenticated access to diagnostics console
    Verify that user accounts exist with privileges to access the diagnostics console. Check user roles under iDRAC Settings > User Authentication, or via RACADM: racadm get iDRAC.Users.1 through racadm get iDRAC.Users.16.
    Affected if Any user account (including remote directory accounts) has sufficient privileges to access and use the diagnostics console feature.

You are affected if you are running Dell iDRAC6 Modular (any version) OR iDRAC6 Monolithic with firmware below 2.91, AND the web-based diagnostics console is enabled with at least one authenticated user able to access it.

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.

From vendor data
Upgrade available Upgrade to 2.91 or later
Fixed in 2.91
Interim mitigation

Update iDRAC6 firmware to version 2.91 or later (monolithic); apply vendor patches for modular versions. Restrict diagnostics console access to essential personnel only until patching is complete.

Fix this in Idrac6 Modular Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,440
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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