CVE-2021-36302
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 · uneditedAll Dell EMC Integrated System for Microsoft Azure Stack Hub versions contain a privilege escalation vulnerability. A remote malicious user with standard level JEA credentials may potentially exploit this vulnerability to elevate privileges and take over the 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 · moderate confidenceThis vulnerability affects Dell EMC Integrated System for Microsoft Azure Stack Hub across all versions. It allows a remote attacker with standard JEA (Just Enough Administration) credentials to escalate privileges beyond their intended permissions, potentially achieving full system compromise. The CVSS 9.9 score indicates critical severity with low attack complexity and no required user interaction.
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<= 2204CVSS 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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the Azure Stack Hub firmware versionAccess the Azure Stack Hub administrator portal or use the Azure Stack Hub Admin API to retrieve the current firmware/build version. This is typically found in the 'Region management' or 'Updates' blade of the Azure Stack Hub administrator dashboard.Affected if The firmware version is 2204 or lower (any version up to and including 2204).
-
Confirm JEA is enabled on the systemCheck the Just Enough Administration (JEA) configuration on the Azure Stack Hub management endpoints. This can be done by reviewing the PowerShell session configurations registered on the management VMs. Use Get-PSSessionConfiguration in an elevated PowerShell session on the management infrastructure.Affected if JEA session configurations exist and are registered on the Azure Stack Hub management endpoints.
-
Verify remote JEA access is permittedReview the JEA endpoint configuration to determine whether it accepts remote connections. Check the Permission model setting on the JEA session configuration. This is typically configured in the role capability files or through the Azure Stack Hub administrative interface.Affected if JEA endpoints are configured to allow remote session connections (network-based access).
-
Review JEA role definitions for permission boundariesExamine the role capability files assigned to standard users. These files define what cmdlets and parameters are accessible. Check whether the roles permit access to cmdlets that could be used for privilege escalation, such as those allowing modifications to user roles, permissions, or execution of arbitrary code.Affected if Standard user JEA roles have cmdlets that can bypass permission boundaries or execute elevated operations.
The environment is affected if the Azure Stack Hub firmware version is 2204 or lower AND JEA is enabled with remote access and has role definitions that permit standard users to exceed their intended permission boundaries.
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 dataApply Dell-provided patches for CVE-2021-36302 and review JEA role definitions to ensure standard users cannot bypass permission boundaries. Consider restricting remote JEA access until patches are applied.
- Consultation8.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-36302 — 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-36302 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