dbcve.org
Cyber FilesApplication · Acronis

CVE-2024-49389

HIGH · 7.8 CVSS v3.1 Published 2024-10-17
Fix available
A fix is available. Upgrade to 9.0 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 Cyber Files (Windows) before build 9.0.0x24.

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

Local privilege escalation vulnerability in Acronis Cyber Files for Windows due to insecure folder permissions. An attacker with local access to the affected system could exploit misconfigured folder permissions to gain elevated privileges. The vulnerability exists in versions before build 9.0.0x24.

MitigationUpgrade Acronis Cyber Files to build 9.0.0x24 or later to obtain the security patch that corrects the folder permission configuration.

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
Cyber FilesApplication
Affected:< 9.0

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 Cyber Files is installed
    Check for the product in Windows Programs and Features, or look for the installation directory (commonly C:\Program Files\Acronis\Cyber Files or similar), or query the Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for an entry named 'Acronis Cyber Files'
    Affected if The product is found installed on the system
  2. Check installed version and build number
    Locate version information in the Windows Registry under HKLM\SOFTWARE\Acronis\Cyber Files\About, or check the version displayed in Programs and Features, or examine the version info of the main executable in the installation folder
    Affected if The version displayed is earlier than build 9.0.0x24, or the major version shows anything less than 9.0 (e.g., 8.x, 7.x)
  3. Inspect folder permissions on Acronis installation directories
    Right-click the Acronis Cyber Files installation folder in File Explorer, select Properties, then go to the Security tab. Check the permissions for Users or Authenticated Users groups. Alternatively, run 'icacls "<install_path>"' from an elevated command prompt to view effective permissions
    Affected if Users or non-admin accounts have Modify, Write, or Full Control permissions on program folders that should be admin-only
  4. Check for weak ACLs on service executable folders
    Run 'icacls "<install_path>\*" /T' to recursively list all ACLs on subfolders and files. Look for entries granting Write or Modify access to the Users group or BUILTIN\Users on folders containing executables or DLLs
    Affected if Any executable-containing folder grants write/modify access to standard users, allowing privilege escalation via DLL hijacking or binary replacement

The system is affected if Acronis Cyber Files is installed with a version before build 9.0.0x24 and folder permissions grant non-admin users write access to program directories.

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 9.0 or later
Fixed in 9.0
Interim mitigation

Upgrade Acronis Cyber Files to build 9.0.0x24 or later to obtain the security patch that corrects the folder permission configuration.

Recommended fix High confidence

Acronis Cyber Files build 9.0.0x24 or later

  1. Identify the currently installed Acronis Cyber Files (Windows) version by checking the program in Add/Remove Programs or the installation directory
  2. Download Acronis Cyber Files version 9.0.0x24 or later from the official Acronis download center or your licensed portal
  3. Before upgrading, backup any critical data and ensure you have a system restore point
  4. Run the installer with administrative privileges and follow the on-screen prompts to upgrade the installation
  5. After upgrade completes, verify the new version is 9.0.0x24 or higher in Add/Remove Programs
  6. Restart any services or the system if prompted by the installer

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

Fix this in Cyber Files Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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