dbcve.org
True ImageApplication · Acronis

CVE-2022-24114

HIGH · 7.0 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 →
72/100
Remediation priority · Elevated
Zero-click

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 race condition on application startup. The following products are affected: Acronis Cyber Protect Home Office (macOS) before build 39605, Acronis True Image 2021 (macOS) 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 · moderate confidence

A local privilege escalation vulnerability exists in Acronis Cyber Protect Home Office and Acronis True Image 2021 for macOS due to a race condition during application startup. The vulnerability allows an unprivileged local attacker to exploit a time-of-check-time-of-use (TOCTOU) window to gain elevated privileges. The issue is fixed in build 39605 for Acronis Cyber Protect Home Office and build 39287 for Acronis True Image 2021.

MitigationUpdate Acronis Cyber Protect Home Office to build 39605 or later, and Acronis True Image 2021 to build 39287 or later. Alternatively, restrict local untrusted user access to the system pending the update.

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

CVSS:3.1/AV:L/AC:H/PR:L/UI:N/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 if Acronis software is installed
    Run: ls /Applications/ | grep -i acronis OR system_profiler SPApplicationsDataType | grep -i acronis
    Affected if Either Acronis True Image 2021 or Acronis Cyber Protect Home Office appears in the installed applications list
  2. Find the build number for Acronis True Image 2021
    Run: mdls -name CFBundleVersion /Applications/Acronis\ True\ Image.app/ (or check Info.plist for CFBundleVersion)
    Affected if The build number is lower than 39287 (fixed version is 39287 or later)
  3. Find the build number for Acronis Cyber Protect Home Office
    Run: mdls -name CFBundleVersion /Applications/Acronis\ Cyber\ Protect\ Home\ Office.app/ (or check Info.plist for CFBundleVersion)
    Affected if The build number is lower than 39605 (fixed version is 39605 or later)
  4. Confirm the product name matches the installed application
    Run: mdls -name CFBundleName /Applications/Acronis\ True\ Image.app/ OR /Applications/Acronis\ Cyber\ Protect\ Home\ Office.app/ to verify exact product
    Affected if Product is Acronis True Image 2021 or Acronis Cyber Protect Home Office and version check fails

You are affected if Acronis True Image 2021 is installed with build lower than 39287, OR Acronis Cyber Protect Home Office is installed with build lower than 39605.

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 39605 or later, and Acronis True Image 2021 to build 39287 or later. Alternatively, restrict local untrusted user access to the system pending the update.

Recommended fix High confidence

Acronis True Image 2021 build 39287+ or Acronis Cyber Protect Home Office build 39605+ (macOS)

  1. 1. Identify the currently installed Acronis product (True Image 2021 or Cyber Protect Home Office) on the macOS system
  2. 2. Check the current build version of the installed Acronis application
  3. 3. For Acronis True Image 2021 users: upgrade to build 39287 or later
  4. 4. For Acronis Cyber Protect Home Office users: upgrade to build 39605 or later
  5. 5. Download the updated version from the official Acronis website or through the product's built-in update mechanism
  6. 6. Install the updated build and restart the system if required
  7. 7. Verify the installed build number matches or exceeds the minimum fixed version for your product

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

Fix this in True Image Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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