dbcve.org
Snap DeployApplication · Acronis

CVE-2024-34019

HIGH · 7.3 CVSS v3.1 Published 2024-08-29
Fix available
A fix is available. Upgrade to 6 or later.
See remediation →
73/100
Remediation priority · Elevated

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 DLL hijacking vulnerability. The following products are affected: Acronis Snap Deploy (Windows) before build 4569.

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

Acronis Snap Deploy for Windows contains a DLL hijacking vulnerability that allows a local attacker to escalate privileges by placing a malicious DLL in a location where the application loads DLLs from an unintended path, potentially achieving code execution with elevated (system) privileges.

MitigationUpdate Acronis Snap Deploy to build 4569 or later. As an interim control, verify that directories from which the application loads DLLs have restrictive permissions to prevent unprivileged users from placing arbitrary DLL files.

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

CVSS:3.1/AV:L/AC:L/PR:L/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. Identify if Acronis Snap Deploy is installed
    Check for the presence of Acronis Snap Deploy in the system registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall or look for the installation directory (typically C:\Program Files\Acronis\Snap Deploy or C:\Program Files (x86)\Acronis\Snap Deploy)
    Affected if Acronis Snap Deploy for Windows is found on the system
  2. Determine installed version
    Open Add or Remove Programs, locate Acronis Snap Deploy, and note the displayed version number. Alternatively, right-click the main executable (typically snapdeploy.exe or similar) in the installation folder, select Properties, and check the Details tab for version information.
    Affected if Version is listed as less than 6 or exactly version 6 (any minor version)
  3. Check build number for version 6 installations
    If the version shows as 6.x, locate the Acronis Snap Deploy executable in its installation folder, right-click and view Properties, or right-click the installer MSI if available, to find the build or revision number.
    Affected if Build number is below 4569 (if version displays as 6.x)
  4. Verify service running with elevated privileges
    Open Services (services.msc), locate the Acronis Snap Deploy service, right-click and select Properties, and check the 'Log On As' account. A service running as Local System or a domain admin account indicates potential for privilege escalation if DLL hijacking is exploitable.
    Affected if Service runs as Local System Account, Network Service, or a privileged user account
  5. Check directory permissions on installation folder
    Navigate to the Acronis Snap Deploy installation directory, right-click the folder, select Properties, go to the Security tab, and review which users have Write or Modify permissions to subfolders where the application loads executables or DLLs.
    Affected if Non-privileged users (such as standard users or Authenticated Users) have Write or Modify access to directories from which the application loads DLLs

The environment is affected if Acronis Snap Deploy for Windows version 6 (with build below 4569) or any version below 6 is installed, and the installation directory permissions allow non-privileged users to write files to locations from which the application loads DLLs.

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 4569 or later. As an interim control, verify that directories from which the application loads DLLs have restrictive permissions to prevent unprivileged users from placing arbitrary DLL files.

Recommended fix Moderate confidence

Acronis Snap Deploy build 4569 or later

  1. Identify the currently installed Acronis Snap Deploy version by checking the software's About or Help section
  2. Download Acronis Snap Deploy build 4569 or later from the official Acronis download portal or your licensed customer portal
  3. Uninstall the current vulnerable version of Acronis Snap Deploy using the standard Windows uninstall process
  4. Install the new version (build 4569 or later) by running the downloaded installer with appropriate administrative privileges
  5. Verify the installation was successful by confirming the build number is 4569 or higher
Caveat Standard version upgrade within same major release - minimal risk, but test in non-production environment first if possible

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
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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