CVE-2021-21510
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 iDRAC8 versions prior to 2.75.100.75 contain a host header injection vulnerability. A remote unauthenticated attacker may potentially exploit this vulnerability by injecting arbitrary ‘Host’ header values to poison a web-cache or trigger redirections.
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 confidenceDell iDRAC8 versions prior to 2.75.100.75 contain a host header injection vulnerability. A remote unauthenticated attacker can inject arbitrary Host header values to poison web caches or trigger malicious redirections, potentially enabling further attacks such as cache-based XSS or phishing via redirected URLs.
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.75.100.75CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
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.
-
Check iDRAC8 firmware version via web interfaceLog into the iDRAC web UI (https://<idrac-ip>) and navigate to System > Overview or iDRAC Settings > Overview. Locate the Firmware Version field.Affected if The displayed version is less than 2.75.100.75 (e.g., 2.70.00.00, 2.65.50.10)
-
Check iDRAC8 firmware version via racadm CLIRun the command 'racadm -r <idrac-ip> -u <username> -p <password> getversion' or 'racadm getsysinfo' from a management station with Dell OpenManage tools installed.Affected if The output shows a firmware version below 2.75.100.75
-
Check iDRAC8 firmware version via Redfish APISend a GET request to https://<idrac-ip>/redfish/v1/Managers/iDRAC.Embedded.1 and parse the FirmwareVersion field in the response.Affected if The FirmwareVersion value is less than 2.75.100.75
-
Verify iDRAC web interface is network-accessibleConfirm the iDRAC8 web interface port (HTTPS port 443 or HTTP port 80) is reachable from external networks or untrusted segments using 'curl -I https://<idrac-ip>' or a port scanner.Affected if The web interface is exposed and the version is below 2.75.100.75 (the vulnerability is remotely exploitable via HTTP requests)
You are affected if the iDRAC8 firmware version is below 2.75.100.75 AND the iDRAC web interface is network-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.
From vendor data2.75.100.75
Update Dell iDRAC8 firmware to version 2.75.100.75 or later. Schedule a maintenance window to apply the patch through Dell's recommended iDRAC update procedure.
- Consultation4.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,912.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-21510 — 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-21510 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