dbcve.org
Integrated Dell Remote Access Controller 8 FirmwareOperating system · Dell

CVE-2021-36347

HIGH · 7.2 CVSS v3.1 Published 2022-01-25
Fix available
A fix is available. Upgrade to 2.82.82.82 / 5.00.20.00 or later.
See remediation →
78/100
Remediation priority · High
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
iDRAC9 versions prior to 5.00.20.00 and iDRAC8 versions prior to 2.82.82.82 contain a stack-based buffer overflow vulnerability. An authenticated remote attacker with high privileges could potentially exploit this vulnerability to control process execution and gain access to the iDRAC operating 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 stack-based buffer overflow vulnerability in Dell iDRAC9 (versions prior to 5.00.20.00) and iDRAC8 (versions prior to 2.82.82.82) allows an authenticated remote attacker with high privileges to potentially execute arbitrary code and gain access to the iDRAC operating system.

MitigationUpgrade iDRAC9 firmware to version 5.00.20.00 or later and iDRAC8 firmware to version 2.82.82.82 or later to resolve the 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
Integrated Dell Remote Access Controller 8 FirmwareOperating system
Affected:< 2.82.82.82
Integrated Dell Remote Access Controller 9 FirmwareOperating system
Affected:< 5.00.20.00

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

CVSS:3.1/AV:N/AC:L/PR:H/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 model
    Access the iDRAC web interface and check the model number in the overview page, or use racadm command: racadm get iDRAC.Info
    Affected if The model is iDRAC8 or iDRAC9
  2. Retrieve iDRAC firmware version via web interface
    Log into the iDRAC web interface, navigate to Overview > iDRAC Settings > License, or go to the About page to view the Firmware Version
    Affected if The displayed firmware version is lower than 5.00.20.00 for iDRAC9 or lower than 2.82.82.82 for iDRAC8
  3. Retrieve iDRAC firmware version via command line
    Use racadm: racadm get iDRAC.FirmwareInfo or racadm version. For Redfish, send GET request to /redfish/v1/Managers/iDRAC.Embedded.1
    Affected if The firmware version returned is lower than 5.00.20.00 for iDRAC9 or lower than 2.82.82.82 for iDRAC8
  4. Check Lifecycle Controller version during boot
    During server boot, press F10 for Lifecycle Controller, then navigate to Hardware > iDRAC Settings > Version to view firmware version
    Affected if The iDRAC firmware version shown is prior to 5.00.20.00 (iDRAC9) or prior to 2.82.82.82 (iDRAC8)

You are affected if your Dell iDRAC8 firmware is below version 2.82.82.82 or your iDRAC9 firmware is below version 5.00.20.00, and the iDRAC is accessible remotely with high-privilege authentication.

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.82.82.82 / 5.00.20.00 or later
Fixed in 2.82.82.825.00.20.00
Interim mitigation

Upgrade iDRAC9 firmware to version 5.00.20.00 or later and iDRAC8 firmware to version 2.82.82.82 or later to resolve the vulnerability.

Recommended fix High confidence

iDRAC8: upgrade to 2.82.82.82 or later | iDRAC9: upgrade to 5.00.20.00 or later

  1. Identify whether the system uses iDRAC8 or iDRAC9 by checking the iDRAC web interface or using racadm command: racadm get iDRAC.Info
  2. Download the firmware update package from Dell's support website: go to www.dell.com and search for iDRAC8 or iDRAC9 firmware
  3. For iDRAC8: download version 2.82.82.82 or later
  4. For iDRAC9: download version 5.00.20.00 or later
  5. Upload the firmware to iDRAC using the web interface (iDRAC Settings > Maintenance > Firmware Update) or via racadm: racadm update -f firmware_version.exe
  6. Follow the on-screen prompts to complete the firmware update; the iDRAC will automatically reboot during the update process
  7. After the update completes, verify the new firmware version by checking iDRAC web interface or running: racadm get iDRAC.Info
Caveat Firmware updates to iDRAC should be performed carefully; ensure stable power during update and review Dell's firmware update documentation for any specific prerequisites or compatibility considerations

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

Fix this in Integrated Dell Remote Access Controller 8 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,180
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,488.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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