dbcve.org
Cyber FilesApplication · Acronis

CVE-2024-49390

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 DLL hijacking vulnerability in Acronis Cyber Files for Windows (versions before build 9.0.0x24) allows a local attacker to execute arbitrary code with elevated privileges by placing a malicious DLL in a location where the application loads DLLs from an untrusted path.

MitigationUpgrade Acronis Cyber Files to build 9.0.0x24 or later to remediate the DLL hijacking vulnerability.

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. Check installed Acronis Cyber Files version
    Open Windows Settings > Apps > Apps & features, locate Acronis Cyber Files, and note the version number shown. Alternatively, open Programs and Features, find Acronis Cyber Files, and view the version column.
    Affected if The displayed version is earlier than 9.0.0x24, or shows a version number less than 9.0
  2. Verify build number via executable or registry
    Navigate to the Acronis Cyber Files installation directory (typically C:\Program Files\Acronis\CyberFiles or C:\Program Files (x86)\Acronis\CyberFiles), right-click the main executable, select Properties, and check the Details tab for the Product Version or Build number.
    Affected if The build number is lower than 24 (representing 9.0.0x24)
  3. Confirm application is installed and running
    Open Task Manager, look for Acronis Cyber Files processes (such as CyberFiles.exe or related services), or check that the application appears in the system tray.
    Affected if The application is present on the system with a version below 9.0.0x24
  4. Check for DLL loading behavior
    Review the Acronis Cyber Files installation directory for any writable folders where untrusted DLLs could be placed. Pay attention to the application executable's working directory and any folders listed in the system PATH that the application accesses.
    Affected if Any directory accessible to the attacker can be used to place a malicious DLL that the application will load

The environment is affected if Acronis Cyber Files is installed with a version earlier than build 9.0.0x24 (or version 9.0), allowing a local attacker to place a malicious DLL in a path the application loads 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

Upgrade Acronis Cyber Files to build 9.0.0x24 or later to remediate the DLL hijacking vulnerability.

Recommended fix High confidence

Acronis Cyber Files (Windows) build 9.0.0x24 or later

  1. 1. Back up all critical data and configuration files for Acronis Cyber Files before initiating the upgrade.
  2. 2. Download the latest version of Acronis Cyber Files (Windows) from the official Acronis download portal or your licensed distribution channel.
  3. 3. Verify the integrity of the downloaded installer using checksums if provided by Acronis.
  4. 4. Stop all running Acronis Cyber Files services to ensure a clean upgrade process.
  5. 5. Run the installer and follow the on-screen prompts to upgrade to build 9.0.0x24 or later.
  6. 6. After installation completes, verify the installed build version matches the fixed release (9.0.0x24 or higher).
  7. 7. Restart the Acronis Cyber Files services and confirm the application runs normally.
  8. 8. Validate that the vulnerability is remediated by checking the product version matches or exceeds the fixed build.

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-49390 — 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-49390 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