dbcve.org
Incorrect Permission AssignmentWeakness · CWE-732

CVE-2024-49385

MEDIUM · 5.5 CVSS v3.0 Published 2025-01-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 True Image (Windows) before build 41736, Acronis True Image OEM (Windows) before build 42575.

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

This vulnerability in Acronis True Image for Windows allows local attackers to access sensitive information due to improperly configured folder permissions. The insecure permissions on certain directories enable unauthorized reading of potentially confidential data such as backup metadata, credentials, or configuration files that should be protected from non-privileged users.

MitigationUpgrade Acronis True Image to build 41736 or later (or build 42575 for OEM versions) to resolve the permission misconfiguration. Verify that folder permissions restrict access to authorized users only.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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.0/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 True Image installation
    Check for Acronis True Image in the system by searching for the product in Programs and Features, or by checking for the installation directory at C:\Program Files\Acronis\ or C:\Program Files (x86)\Acronis\
    Affected if Acronis True Image is installed on the system
  2. Identify Acronis data directories
    Locate folders under the Acronis installation directory that contain backup metadata, credentials, or configuration files. Common paths include C:\ProgramData\Acronis\, C:\Program Files\Acronis\True Image\, or subdirectories within these locations.
    Affected if Acronis data directories exist on the system
  3. Inspect folder permissions on Acronis directories
    Right-click on the Acronis installation or data folders, select Properties, then go to the Security tab. Click Advanced to view permission entries. Check if Users or Everyone groups have Read & Execute, List Folder Contents, or Read permissions granted.
    Affected if Non-admin users or the Everyone group have Read or List permissions on Acronis directories
  4. Test unauthorized access as a standard user
    If possible, log in as a standard (non-admin) user or use icacls from a command prompt to verify access: icacls "C:\ProgramData\Acronis\" or icacls "C:\Program Files\Acronis\"
    Affected if Standard users can successfully read or list contents of Acronis folders that should be restricted

A user is affected if Acronis True Image is installed and standard non-privileged users have read or list access to Acronis folders containing sensitive backup metadata, credentials, or configuration 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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Acronis True Image to build 41736 or later (or build 42575 for OEM versions) to resolve the permission misconfiguration. Verify that folder permissions restrict access to authorized users only.

Recommended fix Moderate confidence

Acronis True Image build 41736 or later; Acronis True Image OEM build 42575 or later

  1. Open Acronis True Image and navigate to Help > About to identify the current build number
  2. For Acronis True Image (Windows): If the build is lower than 41736, download and install the latest version from the official Acronis website or your vendor portal to obtain build 41736 or later
  3. For Acronis True Image OEM (Windows): If the build is lower than 42575, contact your OEM vendor for the updated build 42575 or later
  4. After upgrade, verify the new build number in Help > About reflects build 41736 (standard) or 42575 (OEM) or higher
  5. Confirm that folder permissions have been corrected by reviewing the installation directory (typically C:\Program Files\Acronis\True Image) - ensure non-admin users do not have write access to sensitive configuration or data folders

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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