CVE-2021-36346
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 · uneditedDell iDRAC 8 prior to version 2.82.82.82 contain a denial of service vulnerability. An unauthenticated remote attacker could potentially exploit this vulnerability to deny access to the iDRAC webserver.
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 · moderate confidenceDell iDRAC 8 versions prior to 2.82.82.82 contain a denial of service vulnerability in the webserver component. An unauthenticated remote attacker can send specially crafted requests to the iDRAC web interface, causing the webserver to become unavailable.
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< 2.82.82.82CVSS 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
- None
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
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 checksWork through these to decide whether this CVE applies to you.
-
Identify iDRAC versionAccess the iDRAC web interface and check the dashboard for firmware version, or use 'racadm get iDRAC.WebServer.1' via the racadm command-line tool, or query the Redfish API at /redfish/v1/Managers/iDRAC.Embedded.1Affected if The firmware version displayed is below 2.82.82.82 (e.g., 2.70.00.00, 2.65.50.10)
-
Verify iDRAC 8 modelConfirm the device is specifically iDRAC 8 (not iDRAC 7 or iDRAC 9). Check the product name in the iDRAC web interface under 'Hardware' > 'iDRAC Settings' > 'Overview', or via 'racadm get iDRAC.Info'Affected if The model is iDRAC 8 and the version is below 2.82.82.82
-
Confirm webserver is enabledCheck if the iDRAC web interface is enabled via 'racadm get iDRAC.WebServer.1' or through the web UI at 'iDRAC Settings' > 'Services' > 'Web Server'. The vulnerability requires the webserver to be active.Affected if WebServer.1.Enable is set to 'Enabled' and the firmware version is below 2.82.82.82
-
Assess network exposureDetermine if the iDRAC web interface (HTTPS port 443) is accessible from untrusted networks. Check firewall rules, VLAN configuration, and whether iDRAC is on an isolated management network. Use 'racadm get iDRAC.NIC.1' to review IP settings.Affected if The iDRAC web interface is exposed to untrusted networks (e.g., directly internet-facing or in an untrusted VLAN) and the version is below 2.82.82.82
You are affected if your Dell iDRAC 8 firmware version is below 2.82.82.82 and the iDRAC webserver is enabled and accessible.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2.82.82.82
Upgrade iDRAC 8 firmware to version 2.82.82.82 or later. If immediate patching is not possible, consider network segmentation to limit exposure to untrusted networks and implement monitoring for unusual iDRAC webserver activity.
iDRAC 8 Firmware version 2.82.82.82 or later
- 1. Identify the current iDRAC 8 firmware version by accessing the iDRAC web interface or using racadm command line tool (e.g., 'racadm get iDRAC.Embedded.1.ServerInfo.1.FirmwareVersion')
- 2. Download the iDRAC 8 firmware version 2.82.82.82 or later from the Dell Support site (support.dell.com) for your specific PowerEdge server model
- 3. Upload the firmware update via the iDRAC web interface under 'Maintenance' > 'Firmware Update', or use racadm: 'racadm update -f <firmware_image_file>'
- 4. Wait for the firmware update to complete; the iDRAC will automatically restart
- 5. Verify the updated firmware version matches 2.82.82.82 or later after the reboot
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2021-36346 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-36346 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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