CVE-2022-35799
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 · uneditedAzure Site Recovery Elevation of Privilege Vulnerability
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 confidenceAzure Site Recovery contains an elevation of privilege vulnerability that could allow an authenticated attacker to gain higher-level permissions within the Azure Site Recovery service, potentially accessing resources or performing actions beyond their assigned role.
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< 9.50.6419.1CVSS 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
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/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.
-
Check Azure Site Recovery provider versionIn Azure Portal, navigate to each Recovery Services vault, then to Site Recovery Infrastructure > For VMware and Physical Machines > Configuration Server, or use PowerShell: Get-AzRecoveryServicesVault -VaultName 'YourVault' | Get-AzRecoveryServicesVaultPropertiesAffected if The installed Azure Site Recovery provider version is below 9.50.6419.1
-
Verify authenticated user access to Site Recovery vaultsIn Azure Portal, go to Recovery Services vaults > Access control (IAM) > Role assignments, or use Az PowerShell: Get-AzRoleAssignment -Scope '/subscriptions/{sub-id}/resourceGroups/{rg-name}/providers/Microsoft.RecoveryServices/vaults/{vault-name}'Affected if Any user or service principal has been granted Contributor, Owner, or Site Recovery-specific roles on the vault
-
Audit Site Recovery-specific role assignmentsReview role assignments specifically for roles containing 'Site Recovery' such as Site Recovery Contributor, Site Recovery Operator, Site Recovery Reader using Get-AzRoleAssignment with -RoleDefinitionName parameterAffected if Users are assigned Site Recovery-specific roles that could be exploited for privilege escalation
-
Review Azure Activity Log for vault operationsIn Azure Portal, go to Recovery Services vault > Activity log, or use Get-AzLog -ResourceGroupName 'YourRG' -ResourceProviderType 'Microsoft.RecoveryServices' to filter recent operationsAffected if Operations show execution from accounts with permissions that exceed their intended role scope
A user is affected if their Azure Site Recovery provider version is below 9.50.6419.1 AND any authenticated users have vault access permissions that could be exploited for elevation beyond their assigned role.
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 · scoped9.50.6419.1
Apply Microsoft's security updates for Azure Site Recovery; review and enforce least-privilege role assignments for Site Recovery vault access; audit existing user permissions to ensure they align with intended access levels.
9.50.6419.1 or later
- Verify current Azure Site Recovery version by checking the ASR settings in the Azure Portal
- Navigate to the Site Recovery vault and check the version under Site Recovery infrastructure
- If the version is below 9.50.6419.1, no manual action is typically required as Azure services are updated by Microsoft automatically
- If immediate remediation is needed, contact Microsoft Azure Support to request the update to version 9.50.6419.1 or later
- Confirm the version has been updated to 9.50.6419.1 or higher after the update is applied
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-35799 — 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-2022-35799 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