dbcve.org
Emc Integrated System For Microsoft Azure Stack Hub FirmwareOperating system · Dell

CVE-2021-21505

CRITICAL · 9.8 CVSS v3.1 Published 2021-05-06
Fix available
A fix is available. Upgrade to after 2011 or later.
See remediation →
100/100
Remediation priority · Urgent
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 Integrated System for Microsoft Azure Stack Hub, versions 1906 – 2011, contain an undocumented default iDRAC account. A remote unauthenticated attacker, with the knowledge of the default credentials, could potentially exploit this to log in to the system to gain root privileges.

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 Integrated System for Microsoft Azure Stack Hub versions 1906-2011 contains an undocumented default iDRAC account with hardcoded credentials. A remote unauthenticated attacker with knowledge of these default credentials can log into the iDRAC interface and gain root privileges on the affected system.

MitigationImmediately change or disable the undocumented default iDRAC credentials on all affected systems. Apply vendor-provided patches for Azure Stack Hub versions 1906-2011 when released to address this 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 Integrated System For Microsoft Azure Stack Hub FirmwareOperating system
Affected:>= 1906, <= 2011

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.1/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 Azure Stack Hub firmware version
    Access the Azure Stack Hub administrator portal or use the Azure Stack Hub Admin API to retrieve the firmware version. Navigate to the infrastructure overview or health and alerts section to find the current firmware/build version.
    Affected if The installed firmware version falls within the range 1906 to 2011 inclusive.
  2. Verify iDRAC version
    Access the iDRAC web interface or use iDRAC racadm command-line tool (racadm get iDRAC.Embedded.1.Info) to confirm the iDRAC firmware version matches the Azure Stack Hub firmware version.
    Affected if The iDRAC firmware version is 1906, 1910, 2005, 2008, or 2011.
  3. Confirm iDRAC network accessibility
    Check if the iDRAC interface is reachable from external networks by reviewing network configuration, firewall rules, and performing a network scan or connectivity test to the iDRAC IP address on ports 443 and 22.
    Affected if The iDRAC interface is exposed to untrusted networks, enabling remote unauthenticated access.
  4. Review iDRAC user accounts
    Log into iDRAC and navigate to iDRAC Settings > Users > Local Users to enumerate all configured iDRAC accounts. Check for any unknown or undocumented accounts beyond the standard administrator account.
    Affected if An undocumented default iDRAC account exists and has not been disabled or had its password changed from the hardcoded default.

The system is affected if it runs Azure Stack Hub firmware versions 1906 through 2011 and the undocumented default iDRAC account with hardcoded credentials remains active and accessible.

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 a release after 2011
Interim mitigation

Immediately change or disable the undocumented default iDRAC credentials on all affected systems. Apply vendor-provided patches for Azure Stack Hub versions 1906-2011 when released to address this vulnerability.

Recommended fix Moderate confidence

Firmware version 2103 or later (Dell EMC Integrated System for Microsoft Azure Stack Hub)

  1. 1. Identify the current firmware version of the Dell EMC Integrated System for Microsoft Azure Stack Hub by accessing the iDRAC web interface or using racadm command-line tool.
  2. 2. Navigate to the Dell support website (www.dell.com) and search for Dell EMC Azure Stack Hub firmware updates.
  3. 3. Download the latest firmware version (version 2103 or later) from the official Dell support page.
  4. 4. Review the firmware release notes to confirm the version includes the fix for CVE-2021-21505 (removal of undocumented default iDRAC account).
  5. 5. Apply the firmware update following Dell's documented upgrade procedure, which typically involves uploading the update via iDRAC and rebooting the system.
  6. 6. After the update, verify that the undocumented default iDRAC account has been removed by checking the iDRAC user list.
  7. 7. Ensure any legitimate iDRAC user accounts are properly configured with strong, unique passwords.
Caveat Firmware updates to Azure Stack Hub appliances may require maintenance window and should be tested in a non-production environment first; ensure proper backups and rollback procedures are in place.

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

Fix this in Emc Integrated System For Microsoft Azure Stack Hub Firmware 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-2021-21505 — 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-21505 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