dbcve.org
Cyber Protect Home OfficeApplication · Acronis

CVE-2023-48677

HIGH · 7.8 CVSS v3.1 Published 2023-12-12
Fix available
A fix is available. Upgrade to 40901 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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 Home Office (Windows) before build 40901, Acronis Cyber Protect Cloud Agent (Windows) before build 39378, Acronis Cyber Protect 16 (Windows) before build 39938, Acronis True Image OEM (Windows) before build 42575.

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

DLL hijacking vulnerability in Acronis Windows products allows local privilege escalation. An attacker can place a malicious DLL in a location where the vulnerable application loads it, causing arbitrary code execution with elevated privileges.

MitigationUpdate affected Acronis products to the specified build versions or later: Cyber Protect Home Office to build 40901+, Cloud Agent to build 39378+, Cyber Protect 16 to build 39938+, and True Image OEM to build 42575+.

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 Protect Home OfficeApplication
Affected:< 40901

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

CVSS:3.1/AV:L/AC:L/PR:N/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 Home Office installation
    Check the Windows registry for the installation path at HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{GUID} or look in C:\Program Files\Acronis\ or C:\Program Files (x86)\Acronis\ for Cyber Protect Home Office folders.
    Affected if The product is installed in the system
  2. Identify the installed build version
    Right-click the main executable (typically CyberProtectHomeOffice.exe or similar), select Properties, and check the File Version or Product Version field. Alternatively, open Acronis Cyber Protect Home Office, go to Help > About to view the build number.
    Affected if The build number displayed is less than 40901
  3. Verify DLL search order vulnerability exists
    Check if non-system directories are in the system PATH environment variable that could allow an attacker to place a malicious DLL. Review the PATH variable at System Properties > Environment Variables > System variables > Path.
    Affected if The PATH contains writable directories (such as user-writable folders) before system directories and the application loads DLLs without fully qualifying the path
  4. Confirm the service runs with elevated privileges
    Open Services (services.msc), find the Acronis service related to Cyber Protect Home Office, right-click and select Properties. Check the 'Log on as' account - if it runs as Local System or another privileged account, privilege escalation is possible.
    Affected if The Acronis service runs under Local System, Administrator, or another privileged account

A user is affected if Acronis Cyber Protect Home Office is installed with a build number below 40901 and runs as a privileged service while the DLL search path includes writable 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 40901 or later
Fixed in 40901
Interim mitigation

Update affected Acronis products to the specified build versions or later: Cyber Protect Home Office to build 40901+, Cloud Agent to build 39378+, Cyber Protect 16 to build 39938+, and True Image OEM to build 42575+.

Recommended fix High confidence

Acronis Cyber Protect Home Office build 40901; Cyber Protect Cloud Agent build 39378; Cyber Protect 16 build 39938; Acronis True Image OEM build 42575

  1. 1. Identify the specific Acronis product installed (Cyber Protect Home Office, Cyber Protect Cloud Agent, Cyber Protect 16, or True Image OEM) and note the current build version.
  2. 2. Visit the official Acronis security advisory at security-advisory.acronis.com to obtain the correct updated installer for your product.
  3. 3. Download the updated build: Cyber Protect Home Office build 40901 or later, Cyber Protect Cloud Agent build 39378 or later, Cyber Protect 16 build 39938 or later, or True Image OEM build 42575 or later.
  4. 4. Close any running Acronis applications and ensure no backup operations are in progress.
  5. 5. Run the downloaded installer to apply the update, following standard Acronis installation procedures.
  6. 6. After installation completes, verify the product shows the updated build number in Help > About or the product console.
Caveat Standard Acronis update procedure; ensure backups are not running during upgrade; may require system restart

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

Fix this in Cyber Protect Home Office Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,400
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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