dbcve.org
True ImageApplication · Acronis

CVE-2021-44205

HIGH · 7.3 CVSS v3.1 Published 2022-02-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 Protect Home Office (Windows) before build 39612, Acronis True Image 2021 (Windows) before build 39287

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

Local privilege escalation vulnerability in Acronis Cyber Protect Home Office and Acronis True Image 2021 on Windows. The vulnerability allows DLL hijacking, where a malicious DLL can be loaded by the application due to insecure DLL loading path, potentially executing with elevated privileges.

MitigationUpdate Acronis Cyber Protect Home Office to build 39612 or later, and Acronis True Image 2021 to build 39287 or later, as these patches address the insecure DLL loading.

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
True ImageApplication
Affected:= 2021
Cyber Protect Home OfficeApplication
Affected:all versions

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. Identify installed Acronis True Image version
    Check the Windows registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{GUID} for DisplayVersion, or use PowerShell: Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*' | Where-Object {$_.DisplayName -like '*True Image*2021*'} | Select-Object DisplayName, DisplayVersion
    Affected if DisplayVersion shows 2021 (any build) AND the build number is lower than 39287, or if version cannot be determined but the product is named True Image 2021
  2. Identify installed Acronis Cyber Protect Home Office version
    Check the Windows registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{GUID} for DisplayVersion or DisplayVersion, or use PowerShell: Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*' | Where-Object {$_.DisplayName -like '*Cyber Protect Home Office*'} | Select-Object DisplayName, DisplayVersion
    Affected if The product is installed (any version displayed) AND the build number is lower than 39612, or if the build number cannot be determined
  3. Locate Acronis executable to verify installation
    Search for Acronis executables in Program Files directories: dir /s /b 'C:\Program Files\Acronis\*.exe' 2>nul | findstr /i 'TrueImage CyberProtect'
    Affected if True Image 2021 or Cyber Protect Home Office executables are found in the file system, confirming the product is installed and potentially vulnerable

If Acronis True Image 2021 with build lower than 39287 or Acronis Cyber Protect Home Office with build lower than 39612 is installed, the environment is affected by this DLL hijacking vulnerability.

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

Update Acronis Cyber Protect Home Office to build 39612 or later, and Acronis True Image 2021 to build 39287 or later, as these patches address the insecure DLL loading.

Recommended fix High confidence

Acronis True Image 2021 build 39287 or later, or Acronis Cyber Protect Home Office build 39612 or later

  1. 1. Identify the currently installed Acronis product (True Image 2021 or Cyber Protect Home Office)
  2. 2. Open Acronis Cyber Protect Home Office or True Image 2021
  3. 3. Navigate to Help > About or check the current build number in the application
  4. 4. If True Image 2021 is below build 39287, or Cyber Protect Home Office is below build 39612, proceed to update
  5. 5. Open Acronis Backup and Recovery tool or use the built-in update feature
  6. 6. Check for updates and install the latest version
  7. 7. Verify the installed build number meets or exceeds the fixed version (True Image 2021: 39287+, Cyber Protect Home Office: 39612+)
  8. 8. Restart the system if required after the update
Caveat Minor - routine software update, no expected breaking changes for typical users

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

Fix this in True Image Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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