Skip to main content
Vulnerability Database/CVE-2024-55543

CVE-2024-55543: Acronis Cyber Protect Privilege Escalation

CVE-2024-55543 is a local privilege escalation flaw in Acronis Cyber Protect caused by DLL hijacking. This vulnerability affects Windows systems and allows unauthorized elevation of privileges. This post explains its impact, affected versions, and mitigation steps.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2024-55543 Overview

CVE-2024-55543 is a local privilege escalation vulnerability in Acronis Cyber Protect 16 for Windows. The flaw stems from insecure DLL loading behavior, classified as [CWE-427] Uncontrolled Search Path Element. A local attacker who can place a malicious Dynamic Link Library (DLL) in a search path consulted by an Acronis process can achieve code execution in the context of that process. Acronis addressed the issue in build 39169.

Critical Impact

Successful exploitation grants attackers elevated privileges on the host, allowing full compromise of confidentiality, integrity, and availability of the affected system.

Affected Products

  • Acronis Cyber Protect 16 (Windows) — base release
  • Acronis Cyber Protect 16 (Windows) — Update 1 and Update 2
  • All Acronis Cyber Protect 16 (Windows) builds prior to 39169

Discovery Timeline

  • 2025-01-02 - CVE-2024-55543 published to the National Vulnerability Database (NVD)
  • 2026-06-17 - Last updated in NVD database

Technical Details for CVE-2024-55543

Vulnerability Analysis

CVE-2024-55543 is a DLL hijacking (also known as DLL preloading or binary planting) vulnerability affecting Acronis Cyber Protect 16 on Windows. The weakness is categorized under [CWE-427] Uncontrolled Search Path Element. When an Acronis executable loads a DLL by name rather than by absolute path, Windows searches a defined sequence of directories to locate the library. An attacker who controls any writable directory in that search sequence can place a malicious DLL that the trusted Acronis process will load and execute.

Because Acronis Cyber Protect components frequently run with SYSTEM or elevated service privileges, the loaded payload inherits those privileges. This converts a limited local foothold into full system compromise.

Root Cause

The root cause is insecure DLL resolution during process initialization or module loading. The vulnerable Acronis binaries do not enforce fully qualified paths, do not validate code signatures of dependent libraries, and do not use SetDefaultDllDirectories or LoadLibraryEx with secure search flags to constrain the DLL search path. User interaction is required, typically through launching an affected Acronis component while the planted DLL is present on disk.

Attack Vector

Exploitation requires local access and user interaction. A representative attack chain follows these steps:

  1. The attacker obtains code execution as a low-privileged user on a host running Acronis Cyber Protect 16.
  2. The attacker writes a crafted DLL to a directory that appears earlier in the Windows DLL search order than the legitimate library location, or into the application's own directory.
  3. A user or scheduled task invokes an affected Acronis executable.
  4. The Acronis process resolves the DLL name against the attacker-controlled path and loads the malicious library.
  5. DllMain of the planted DLL executes in the privileged Acronis process context, giving the attacker elevated privileges.

No verified public proof-of-concept has been published. See the Acronis Security Advisory SEC-6418 for vendor-supplied details.

Detection Methods for CVE-2024-55543

Indicators of Compromise

  • Unsigned or unexpectedly signed DLLs located in Acronis installation directories or in directories writable by non-administrative users.
  • Acronis service processes loading modules from user-writable paths such as %TEMP%, %APPDATA%, or the current working directory.
  • Child processes spawned by Acronis executables that are inconsistent with normal backup, agent, or management workflows.

Detection Strategies

  • Audit module load events (Sysmon Event ID 7) where the ImageLoaded path is outside expected Acronis program directories.
  • Correlate process creation events (Sysmon Event ID 1) with parent Acronis binaries that spawn interpreters such as cmd.exe, powershell.exe, or rundll32.exe.
  • Hunt for file write events (Sysmon Event ID 11) that create .dll files in directories co-located with Acronis executables, especially by non-SYSTEM accounts.

Monitoring Recommendations

  • Enable Windows code integrity logging and PowerShell script block logging to capture post-exploitation behavior.
  • Monitor Acronis service accounts for anomalous network connections, token manipulation, or persistence activity.
  • Baseline the set of DLLs legitimately loaded by Acronis processes and alert on deviations.

How to Mitigate CVE-2024-55543

Immediate Actions Required

  • Upgrade Acronis Cyber Protect 16 for Windows to build 39169 or later on all affected hosts.
  • Inventory endpoints running Acronis Cyber Protect 16 base, Update 1, or Update 2 and prioritize them for patching.
  • Restrict interactive logon and local write permissions on directories referenced by Acronis executables and services.

Patch Information

Acronis released a fixed build for Cyber Protect 16 on Windows. Administrators should apply build 39169 or later as documented in the Acronis Security Advisory SEC-6418. Verify successful upgrade by checking the installed component versions through the Acronis management console.

Workarounds

  • If patching must be delayed, enforce least privilege on all Acronis installation directories and remove write permissions for standard users.
  • Apply application control policies, such as Windows Defender Application Control (WDAC) or AppLocker, to permit only signed Acronis-authored DLLs in process address spaces.
  • Monitor for the indicators and detection patterns above until the fixed build is deployed.
bash
# Example PowerShell command to list the installed Acronis Cyber Protect build
Get-ItemProperty 'HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\*' |
  Where-Object { $_.DisplayName -like 'Acronis Cyber Protect*' } |
  Select-Object DisplayName, DisplayVersion, InstallLocation

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.