CVE-2022-35774VulnerabilityPublished 9 Aug 2022Updated 29 May 2025

CVE-2022-35774: Microsoft Azure Site Recovery VMWare to Azure · Elevation of Privilege

Affects Microsoft Azure Site Recovery VMWare to AzureSource CVE Database V5

Not known to be exploited · CVSS 4.9 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

4.9Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 2.0% chance of exploitation in 30 days – higher than 80% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N/E:P/RL:O/RC:C

Base metrics

Attack Vector: Network
Attack Complexity: Low
Privileges Required: High
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Temporal metrics

Exploit Code Maturity: Proof-of-Concept
Remediation Level: Official Fix
Report Confidence: Confirmed

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.
Exploit Code Maturity: Proof-of-Concept: Proof-of-concept exploit code is available, or an attack demonstration is not practical for most systems. The code or technique is not functional in all situations and may require substantial modification by a skilled attacker.
Remediation Level: Official Fix: A complete vendor solution is available. Either the vendor has issued an official patch, or an upgrade is available.
Report Confidence: Confirmed: Detailed reports exist, or functional reproduction is possible (functional exploits may provide this). Source code is available to independently verify the assertions of the research, or the author or vendor of the affected code has confirmed the presence of the vulnerability.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 9 Aug 2022
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
NuGetmicrosoft.azure.siterecovery.vmwaretoazure`pkg:nuget/microsoft.azure.siterecovery.vmwaretoazure`Other threats	Affected =9.0	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should prioritize the following mitigation steps: 1) Monitor Microsoft’s official security advisories closely for the release of patches addressing CVE-2022-35774 and apply them promptly once available. 2) Restrict administrative access to Azure Site Recovery environments to the minimum necessary personnel and enforce strict role-based access controls (RBAC) to limit the number of users with high privileges. 3) Implement network segmentation and firewall rules to limit exposure of Azure Site Recovery management interfaces to trusted networks only. 4) Enable and review detailed logging and monitoring of Azure Site Recovery activities to detect anomalous privilege escalations or unauthorized access attempts. 5) Conduct regular security audits and penetration testing focusing on privilege management within Azure Site Recovery configurations. 6) Educate administrators on the risks of privilege escalation vulnerabilities and enforce the principle of least privilege in all cloud management operations. These measures go beyond generic patching advice by emphasizing access control hardening and proactive monitoring tailored to the affected product and environment.

Description

Azure Site Recovery Elevation of Privilege Vulnerability

Impact

For European organizations, the impact of this vulnerability could be substantial, especially for enterprises relying on Azure Site Recovery for business continuity and disaster recovery of VMware workloads. An attacker exploiting this vulnerability could gain unauthorized access to sensitive data replicated or managed within the Azure environment, potentially leading to data breaches or exposure of confidential information. Since Azure Site Recovery is integral to maintaining operational resilience, any compromise could disrupt recovery processes or lead to unauthorized data access during failover scenarios. This could affect sectors with stringent data protection requirements such as finance, healthcare, and government institutions across Europe. Furthermore, the exposure of sensitive replication data could contravene GDPR mandates, leading to regulatory penalties. Although no active exploits are known, the presence of this vulnerability in a critical cloud service component necessitates immediate attention to prevent potential targeted attacks.

CWE-269Improper Privilege Management (opens in a new tab)
Class weaknessLikelihood of exploit: MediumOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Architecture and Design · Operation
Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
Architecture and Design · Separation of Privilege
Follow the principle of least privilege when assigning access rights to entities in a software system.
Architecture and Design · Separation of Privilege
Consider following the principle of separation of privilege. Require multiple conditions to be met before permitting access to a system resource.
OWASP Cheat Sheets
Docker Security (opens in a new tab)
Third Party Javascript Management (opens in a new tab)
Virtual Patching (opens in a new tab)
Secure Design Principles (opens in a new tab)
OWASP ASVS 4.0.3
V1.4.4 (opens in a new tab)
V1.4.5 (opens in a new tab)
V1.10.1 (opens in a new tab)
Attack patterns
Restful Privilege Elevation (opens in a new tab)
Privilege Abuse (opens in a new tab)
Privilege Escalation (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

msrc.microsoft.com/update-guide/vulnerability/CVE-2022-35774 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 7 Jul 2025, 22:27 UTC

WeaknessesCWE-269

Technical details

References

Community reviews

Related threats