dbcve.org
Cyber FilesApplication · Acronis

CVE-2024-49391

HIGH · 7.3 CVSS v3.1 Published 2024-10-17
Fix available
A fix is available. Upgrade to 9.0 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 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 · moderate confidence

A local privilege escalation vulnerability exists in Acronis Cyber Files for Windows due to improper DLL loading. The application is susceptible to DLL hijacking, allowing a local attacker to execute arbitrary code with elevated privileges by placing a malicious DLL in a location where the application loads DLLs from.

MitigationUpdate Acronis Cyber Files to build 9.0.0x24 or later. Until then, restrict local user write access to directories from which the application loads DLLs and monitor for unauthorized DLL placement.

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
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. Confirm Acronis Cyber Files is installed
    Open Programs and Features (appwiz.cpl) or check C:\Program Files\Acronis for the Cyber Files directory
    Affected if Acronis Cyber Files appears in installed programs or the Acronis directory exists on the system
  2. Identify installed version
    Right-click the Acronis Cyber Files entry in Programs and Features and select Properties, or check the version info of the main executable in the installation folder
    Affected if The displayed version is below 9.0.0.24 or the build number is unknown or less than 9.0.0.24
  3. Check write access to application directories
    Use icacls or File Explorer security properties to examine ACLs on the Acronis installation directory and its subdirectories
    Affected if Authenticated Users, Users group, or other low-privileged accounts have Write or Modify permissions to directories from which the application loads DLLs
  4. Verify DLL search order behavior
    Use Process Monitor (from Sysinternals) to trace DLL loading when the Acronis Cyber Files service or client starts, filtering by the Acronis process name
    Affected if The application loads DLLs from directories writable by non-privileged users, indicating potential DLL hijacking vector

A system is affected if Acronis Cyber Files version is below 9.0.0.24 and low-privileged users can write to directories where the application loads DLLs from.

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

Update Acronis Cyber Files to build 9.0.0x24 or later. Until then, restrict local user write access to directories from which the application loads DLLs and monitor for unauthorized DLL placement.

Recommended fix Moderate confidence

Acronis Cyber Files build 9.0.0x24 or later (version 9.0)

  1. Verify current installed version of Acronis Cyber Files (Windows) by checking Add/Remove Programs or the application UI
  2. Download Acronis Cyber Files version 9.0.0x24 or later from the official Acronis download center or your licensed distribution channel
  3. Backup any critical data or configuration files associated with Acronis Cyber Files
  4. Uninstall the current version of Acronis Cyber Files through Windows Add/Remove Programs
  5. Install the downloaded version 9.0.0x24 or later
  6. Restart the Windows system if prompted
  7. Verify the installation was successful and the application runs without errors
  8. Confirm the installed build number matches or exceeds 9.0.0x24

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

Fix this in Cyber Files Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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