dbcve.org
Azure Site Recovery Vmware To AzureApplication · Microsoft

CVE-2022-33666

MEDIUM · 6.5 CVSS v3.1 Published 2022-07-12
Fix available
A fix is available. Upgrade to 9.49.6395.1 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
Azure 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 confidence

Azure Site Recovery contains an elevation of privilege vulnerability that could allow an authenticated attacker to gain higher-level access within the service. The vulnerability affects the Site Recovery service infrastructure.

MitigationApply Azure security updates and patches for Azure Site Recovery as they become available through Azure Update Manager or Azure Security Center recommendations.

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
Azure Site Recovery Vmware To AzureApplication
Affected:< 9.49.6395.1

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Azure Site Recovery is in use
    Log into the Azure Portal and navigate to your subscriptions. Check under 'Site Recovery vaults' or search for 'Site Recovery' in the resource search to see if any Site Recovery vaults exist in your subscription.
    Affected if No Site Recovery vaults are found in the subscription, meaning the service is not being used.
  2. Identify Site Recovery for VMware to Azure configuration
    Within any Site Recovery vaults found, navigate to 'Site Recovery infrastructure' and check if 'VMware and physical machines' is enabled as a replication source. This indicates VMware to Azure replication is configured.
    Affected if VMware to Azure replication is not configured; the vulnerability only applies to VMware to Azure scenarios.
  3. Check the Site Recovery agent/infrastructure version
    In the Azure Portal, go to the Site Recovery vault, select 'Site Recovery infrastructure', then 'Configuration servers'. Select the configuration server and check the version number displayed. Alternatively, use Azure CLI command: 'az site-recovery configuration-server show --vault-name <vault-name> --resource-group <rg-name>' and look for the 'version' field.
    Affected if The version displayed is less than 9.49.6395.1, indicating the environment is running a vulnerable version.
  4. Verify replication is active
    In the Site Recovery vault, go to 'Replicated items' to confirm there are active VMware to Azure replications. The vulnerability requires an authenticated attacker with access to the service infrastructure, so active replication indicates the service is fully operational.
    Affected if There are no active VMware to Azure replications, meaning the attack surface is minimal or non-existent even if the version is vulnerable.

The environment is affected if Azure Site Recovery with VMware to Azure replication is configured and the infrastructure version is below 9.49.6395.1.

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 9.49.6395.1 or later
Fixed in 9.49.6395.1
Interim mitigation

Apply Azure security updates and patches for Azure Site Recovery as they become available through Azure Update Manager or Azure Security Center recommendations.

Recommended fix Moderate confidence

9.49.6395.1 or later

  1. Identify the Azure Site Recovery configuration server version currently deployed for VMware to Azure replication
  2. Navigate to the Azure Site Recovery configuration server in the Azure portal or on-premises
  3. Upgrade the configuration server to version 9.49.6395.1 or later
  4. Verify the upgrade completed successfully by checking the configuration server version in the Azure Site Recovery vault
  5. Ensure replication jobs continue正常运行 after the upgrade

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

Fix this in Azure Site Recovery Vmware To Azure Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-33666 — 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-2022-33666 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