dbcve.org
Uncontrolled Search Path (DLL Hijack)Weakness · CWE-427

CVE-2024-34016

MEDIUM · 6.5 CVSS v3.0 Published 2024-09-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
65/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 Protect Cloud Agent (Windows) before build 38235.

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

A DLL hijacking vulnerability in Acronis Cyber Protect Cloud Agent for Windows (versions before build 38235) allows a local attacker to execute arbitrary code with elevated privileges by placing a malicious DLL in a location where the agent loads DLLs from.

MitigationUpgrade Acronis Cyber Protect Cloud Agent to build 38235 or later to remediate this vulnerability.

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
High
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:L/AC:L/PR:H/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. Locate Acronis Cyber Protect Cloud Agent installation directory
    Open File Explorer and navigate to C:\Program Files\Acronis\ or C:\Program Files (x86)\Acronis\ and look for folders named 'Cyber Protect Agent' or similar Acronis agent directories
    Affected if The agent is installed in a standard location and the directory exists on the system
  2. Find the installed build number
    Within the Acronis agent directory, locate a version info file (often named version.ini, version.txt, or similar) or right-click the main executable (typically 'Agent.exe' or 'AA.exe') and select Properties > Details to view the File Version or Product Version
    Affected if The displayed build number is lower than 38235 (for example, 38100, 37000, or any build prior to 38235)
  3. Verify build number via Windows Registry
    Open Registry Editor (regedit), navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Acronis\Global\ or HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Acronis\Global\, and look for a value named 'Build' or 'Version' that shows the installed agent build number
    Affected if The registry shows a build number less than 38235
  4. Check for untrusted DLLs in agent directories
    Examine the Acronis agent installation folder and subdirectories for any DLL files that were recently added or that do not belong to the official installation (compare file creation dates against the agent installation date)
    Affected if Unexpected DLL files exist in the agent directory, particularly in folders where the agent loads DLLs from (such as the bin or lib subdirectories)
  5. Review agent service execution context
    Open Services (services.msc), find the Acronis Cyber Protect service, right-click and select Properties, then note the account listed under 'Log on as' to confirm if it runs with elevated privileges
    Affected if The service runs as SYSTEM or another elevated account, meaning a successful DLL hijacking attack would grant code execution at that privilege level

Your environment is affected if Acronis Cyber Protect Cloud Agent for Windows is installed with a build number lower than 38235, as this version range is vulnerable to DLL hijacking leading to elevated code execution.

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 Cyber Protect Cloud Agent to build 38235 or later to remediate this vulnerability.

Recommended fix High confidence

Acronis Cyber Protect Cloud Agent (Windows) build 38235 or later

  1. Identify the currently installed Acronis Cyber Protect Cloud Agent for Windows version
  2. Navigate to the Acronis download portal or use the built-in update mechanism
  3. Upgrade the agent to build 38235 or later
  4. Verify the installation by checking the agent version

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