dbcve.org
Snap DeployApplication · Acronis

CVE-2022-30695

HIGH · 7.8 CVSS v3.1 Published 2022-05-16
Fix available
A fix is available. Upgrade to 6 or later.
See remediation →
80/100
Remediation priority · High
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
Local privilege escalation due to excessive permissions assigned to child processes. The following products are affected: Acronis Snap Deploy (Windows) before build 3640

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

Local privilege escalation vulnerability in Acronis Snap Deploy (Windows) allows low-privileged users to gain elevated system privileges through child processes that inherit excessive permissions. The affected software assigns overly permissive access rights to spawned child processes, enabling attackers to manipulate these processes to escalate privileges on the local system.

MitigationUpdate Acronis Snap Deploy to build 3640 or later. Prioritize patching systems with local user access as the attack requires local access to the vulnerable machine.

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
Snap DeployApplication
Affected:< 6= 6

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/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. Confirm Acronis Snap Deploy is installed
    Open Control Panel > Programs and Features, or run 'Get-WmiObject -Class Win32_Product | Where-Object {$_.Name -like "*Snap Deploy*"}' in PowerShell. Alternatively, check the registry key HKLM\SOFTWARE\Acronis\SnapDeploy for presence.
    Affected if Acronis Snap Deploy appears in installed programs or registry.
  2. Determine installed version
    Run 'Get-ItemProperty HKLM:\SOFTWARE\Acronis\SnapDeploy\Setup -ErrorAction SilentlyContinue | Select-Object ProductVersion, Build' or check the version column in Programs and Features.
    Affected if Version is less than 6.0.0 or build is earlier than 3640.
  3. Verify Acronis Snap Deploy service is running
    Open Services console (services.msc) or run 'Get-Service -Name "*Acronis*" -ErrorAction SilentlyContinue' to list Acronis-related services. Look for services with 'Snap Deploy' in the name.
    Affected if Any Acronis Snap Deploy service is currently running.
  4. Identify child processes spawned by Acronis services
    Open Task Manager, go to Details tab, and sort by Parent Process (requires enabling 'Parent Process' column via Select Columns). Alternatively, run 'Get-Process | Where-Object {$_.Parent.ProcessName -like "*Acronis*" -or $_.ProcessName -like "*SnapDeploy*"}' in PowerShell.
    Affected if Child processes are running under elevated or system-level accounts and inherit excessive permissions from Acronis parent processes.
  5. Check file permissions on Acronis executable directories
    Navigate to the Acronis installation directory (typically C:\Program Files\Acronis\SnapDeploy\), right-click the folder, go to Properties > Security, and verify which users have Full Control or Modify permissions.
    Affected if Low-privileged users have write or modify access to Acronis executable directories, enabling process manipulation.

A system is affected if Acronis Snap Deploy version 6 or earlier is installed and any Snap Deploy service or process is actively running, allowing low-privileged users to manipulate child processes for privilege escalation.

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

Update Acronis Snap Deploy to build 3640 or later. Prioritize patching systems with local user access as the attack requires local access to the vulnerable machine.

Recommended fix High confidence

Acronis Snap Deploy build 3640 or later

  1. 1. Identify the current version of Acronis Snap Deploy installed on the system
  2. 2. Navigate to the official Acronis download center or your licensed Acronis account
  3. 3. Download Acronis Snap Deploy build 3640 or later for Windows
  4. 4. Follow standard Acronis upgrade procedures - typically run the installer and follow the on-screen prompts
  5. 5. Verify the upgrade was successful by checking the installed build number matches or exceeds 3640

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

Fix this in Snap Deploy Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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