True ImageApplication · Acronis

CVE-2020-15495

HIGH · 7.8 CVSS v3.1 Published 2021-07-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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
Acronis True Image 2019 update 1 through 2020 on macOS allows local privilege escalation due to an insecure XPC service configuration.

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

Acronis True Image 2019 Update 1 through 2020 on macOS contains a local privilege escalation vulnerability stemming from an insecurely configured XPC service. The XPC service, which handles inter-process communication in macOS, lacks proper authorization or access control checks, allowing a local unprivileged attacker to interact with the service and execute code with elevated privileges.

MitigationIf a vendor patch is available, update to the fixed version. Otherwise, remove or disable the vulnerable Acronis True Image XPC service until a patch is released, and review the XPC service's authorization checks and entitlement configuration to enforce proper privilege separation.

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:= 2019= 2020

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

CVSS:3.1/AV:L/AC:L/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 installed Acronis True Image version
    Open Terminal and run: ls /Applications | grep -i 'Acronis True Image' or check via System Settings > Applications. Compare your version to the affected ranges (2019 Update 1 through 2020).
    Affected if The installed version is Acronis True Image 2019 (Update 1 or later) or version 2020 on macOS.
  2. Verify the Acronis XPC service exists
    In Terminal, run: sudo launchctl list | grep -i acronis OR ls /Library/LaunchDaemons/ | grep -i acronis OR ls /Library/LaunchAgents/ | grep -i acronis to locate any Acronis-related XPC or background services.
    Affected if An Acronis XPC service or launch daemon/agent is present on the system.
  3. Confirm the XPC service is running
    Run: ps aux | grep -i acronis to check if any Acronis processes are currently active.
    Affected if The Acronis XPC service process is currently running.
  4. Inspect XPC service entitlement configuration
    Locate the Acronis XPC service binary (typically in /Applications/Acronis True Image.app/Contents/MacOS/ or /Library/Application Support/Acronis/) and inspect its entitlements using: codesign -d --entitlements - /path/to/service 2>/dev/null. Look for any entitlement files in the application bundle.
    Affected if The XPC service lacks proper authorization checks or has overly permissive entitlements (e.g., allows unprivileged users to connect without validation).

A user is affected if Acronis True Image 2019 Update 1 through 2020 is installed on macOS and the vulnerable XPC service is running with improper access controls.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

If a vendor patch is available, update to the fixed version. Otherwise, remove or disable the vulnerable Acronis True Image XPC service until a patch is released, and review the XPC service's authorization checks and entitlement configuration to enforce proper privilege separation.

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-2020-15495 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-2020-15495 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