dbcve.org
Snap DeployApplication · Acronis

CVE-2022-30696

HIGH · 7.8 CVSS v3.1 Published 2022-05-16
Fix available
A fix is available. Upgrade to 6 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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 a DLL hijacking vulnerability. 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 · high confidence

A local privilege escalation vulnerability exists in Acronis Snap Deploy for Windows due to DLL hijacking. The application loads DLLs without using fully qualified paths, allowing an authenticated local attacker to place a malicious DLL in a location where the application will load it, resulting in elevated privileges.

MitigationUpgrade to Acronis Snap Deploy build 3640 or later. If upgrading is not immediately possible, restrict write access to directories in the application's DLL search path to prevent placement of malicious DLLs.

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
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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 installation
    Search for the Acronis Snap Deploy executable (typically snapdeploy.exe or similar) in common installation directories such as C:\Program Files\Acronis or C:\Program Files (x86)\Acronis, or check for the application entry in Add/Remove Programs
    Affected if The application is present on the system
  2. Identify installed version
    Right-click the snapdeploy.exe executable, select Properties, and check the File Version tab. Alternatively, check the Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ for an Acronis Snap Deploy entry and review the DisplayVersion value
    Affected if The version returned is less than 6, or exactly version 6 (any build)
  3. Confirm vulnerable DLL loading behavior
    Review the application's executable and its dependencies using a tool such as Process Monitor or dumpbin /dependents to observe which DLLs the application attempts to load. The vulnerability exists when the application loads DLLs from the current working directory or other writable locations without using fully qualified paths
    Affected if The application loads any DLL from a directory that non-privileged users can write to (indicating unsafe DLL search path usage)
  4. Check user context exposure
    Determine whether any scheduled tasks, services, or shortcuts for Acronis Snap Deploy run with elevated (SYSTEM or administrator) privileges. Review Task Scheduler for tasks related to Acronis Snap Deploy and check the 'Run as' account
    Affected if The application runs with elevated privileges and non-privileged users have write access to directories in the DLL search path

A system is affected if Acronis Snap Deploy version 6 or any earlier version is installed and runs with elevated privileges while allowing non-privileged users to write to directories in the application's DLL search path.

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

Upgrade to Acronis Snap Deploy build 3640 or later. If upgrading is not immediately possible, restrict write access to directories in the application's DLL search path to prevent placement of malicious DLLs.

Recommended fix High confidence

Acronis Snap Deploy build 3640 or later

  1. 1. Ensure you have a complete backup of your current Acronis Snap Deploy configuration and data
  2. 2. Download Acronis Snap Deploy build 3640 or later from the official Acronis download portal or your licensed download area
  3. 3. Stop any running Acronis Snap Deploy services or agents
  4. 4. Run the installer for the new version (build 3640 or later)
  5. 5. Follow the installation wizard prompts to complete the upgrade
  6. 6. After installation, verify the installed build number matches 3640 or later
  7. 7. Restart the Acronis Snap Deploy services
  8. 8. Test that the application functions normally with the new build
Caveat Standard upgrade considerations apply - backup configuration before upgrading; review release notes for any feature changes

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

Fix this in Snap Deploy Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
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,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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