dbcve.org
Snap DeployApplication · Acronis

CVE-2024-34018

MEDIUM · 5.5 CVSS v3.1 Published 2024-08-29
Fix available
A fix is available. Upgrade to 6 or later.
See remediation →
57/100
Remediation priority · Elevated
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
Sensitive information disclosure due to insecure folder permissions. 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 · high confidence

Acronis Snap Deploy for Windows before build 4569 contains insecure folder permissions that allow unauthorized local or potentially network users to read sensitive files stored in certain directories, leading to information disclosure. This is a classic NTFS permission misconfiguration vulnerability.

MitigationUpgrade to build 4569 or later, or manually audit and restrict folder permissions on the affected installation to ensure only authorized users and administrators have read access to sensitive directories.

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
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

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 and version
    Check the installed version by reviewing the program's version information. Common locations: C:\Program Files\Acronis\Snap Deploy\ (or C:\Program Files (x86)\Acronis\Snap Deploy\). Look for executable or DLL file properties, or check Windows Programs and Features for the installed version/build number.
    Affected if The installed version is Acronis Snap Deploy version 6 or lower, or the build number is below 4569.
  2. Locate the Acronis Snap Deploy installation directory
    Identify the primary installation folder where Acronis Snap Deploy stores its program files and data. Typical paths include C:\Program Files\Acronis\Snap Deploy\ or C:\ProgramData\Acronis\Snap Deploy\.
    Affected if The installation directory exists and contains program files for Acronis Snap Deploy version 6 or below build 4569.
  3. Identify sensitive directories within the installation
    Locate directories within the Acronis Snap Deploy installation that store configuration files, credentials, backup data, or other sensitive information. These typically include subfolders for settings, configurations, credentials, or deployed image storage.
    Affected if Sensitive directories exist within the Acronis Snap Deploy installation folder.
  4. Inspect NTFS permissions on sensitive directories
    Right-click each sensitive directory identified, select Properties, then go to the Security tab. Review the list of users and groups with access. Check for permissions granted to non-administrative users, such as 'Users', 'Everyone', 'Authenticated Users', or domain users who should not have access.
    Affected if Users other than Administrators, System, or specifically authorized Acronis service accounts have Read or Full Control permissions to sensitive directories.
  5. Verify unauthorized access via command-line
    Use 'icacls [directory_path]' from an elevated command prompt to view effective permissions on sensitive folders. Look for entries like 'Everyone:(I)(R)', 'Users:(I)(R)', or domain user groups that indicate broader-than-expected access.
    Affected if The icacls output shows Read (R) or Full Control (F) permissions granted to Users, Everyone, or other non-admin accounts.

A system is affected if Acronis Snap Deploy version 6 or below build 4569 is installed AND sensitive directories within the installation have NTFS permissions that allow unauthorized local or network users to read stored files.

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 build 4569 or later, or manually audit and restrict folder permissions on the affected installation to ensure only authorized users and administrators have read access to sensitive directories.

Recommended fix Moderate confidence

Acronis Snap Deploy 6 build 4569 or later

  1. Locate the Acronis Snap Deploy installation in your environment
  2. Download Acronis Snap Deploy version 6 with build 4569 or later from the official Acronis download center or your licensed download area
  3. Backup any existing Snap Deploy configuration data if needed
  4. Uninstall the current version of Acronis Snap Deploy
  5. Install the updated version (build 4569 or later)
  6. Verify the installation completed successfully
  7. Confirm folder permissions have been corrected by checking that sensitive directories no longer have overly permissive access rights

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

Fix this in Snap Deploy Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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