dbcve.org
Snap DeployApplication · Acronis

CVE-2022-30697

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 insecure folder permissions. 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 on Windows caused by insecure folder permissions, allowing a local attacker to manipulate folder ACLs and gain elevated privileges before build 3640.

MitigationUpdate Acronis Snap Deploy to build 3640 or later, or review and harden folder permissions on the installation directories to restrict write access to privileged users only.

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. Verify Acronis Snap Deploy is installed
    Check for the presence of Acronis Snap Deploy in the system: look for the installation directory (commonly under Program Files or Program Files (x86) with 'Acronis' in the name), or check for Snap Deploy services or processes running.
    Affected if Acronis Snap Deploy is found to be installed on the system.
  2. Identify the installed build version
    Locate the Acronis Snap Deploy installation folder and check the version or build information. This may be in the executable properties (right-click on the main .exe file, select Properties, then check the Details tab), or consult Add/Remove Programs for the installed version details.
    Affected if The build version is lower than 3640, or the version is 6.x with build below 3640.
  3. Inspect folder permissions on the installation directory
    Right-click the Acronis Snap Deploy installation folder, go to Properties, then the Security tab. Examine the permissions for users and groups. Check if non-privileged users or groups have Write or Full Control permissions that could allow modification of ACLs or file manipulation.
    Affected if Users with low privileges (such as standard users or authenticated users) have Write or Full Control permissions on the installation directory.
  4. Check for ACL modification capabilities
    Review whether standard users or non-administrator accounts can access the Security settings of folders within the Acronis installation directory and modify permissions. Attempt (in a test environment if possible) to add or modify ACLs on the installation folder using a standard user account.
    Affected if A non-privileged user can successfully modify folder permissions or ACLs on the Acronis Snap Deploy installation directory.

The system is affected if Acronis Snap Deploy is installed with a build version prior to 3640 and the installation directory grants write or modify permissions to non-privileged users.

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, or review and harden folder permissions on the installation directories to restrict write access to privileged users only.

Recommended fix Moderate confidence

Acronis Snap Deploy (Windows) build 3640 or later

  1. 1. Acquire the updated Acronis Snap Deploy installer (build 3640 or later) from the official Acronis download center or your licensed Acronis account
  2. 2. Ensure all Acronis Snap Deploy services are stopped before upgrading
  3. 3. Run the installer with administrative privileges
  4. 4. Follow the installation wizard prompts to complete the upgrade
  5. 5. After installation, verify the build number matches 3640 or higher
  6. 6. Restart the Acronis Snap Deploy services

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

Fix this in Snap Deploy Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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