dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2024-34013

HIGH · 7.8 CVSS v3.0 Published 2024-07-18
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
Local privilege escalation due to OS command injection vulnerability. The following products are affected: Acronis True Image (macOS) before build 41396, Acronis True Image OEM (macOS) before build 42571.

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 True Image for macOS allows an attacker to execute arbitrary OS commands due to insufficient input validation, potentially elevating privileges from user level to root.

MitigationUpgrade Acronis True Image to build 41396 or later (standard version) or build 42571 or later (OEM version).

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

CVSS:3.0/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. Verify Acronis True Image is installed
    Open Finder, go to /Applications folder, or run: ls /Applications | grep -i 'Acronis'
    Affected if Acronis True Image appears in Applications folder
  2. Find installed version and build number
    Right-click Acronis True Image in Applications > Get Info, or run: defaults read /Applications/Acronis\ True\ Image.app/Contents/Info CFBundleShortVersionString 2>/dev/null; defaults read /Applications/Acronis\ True\ Image.app/Contents/Info CFBundleVersion 2>/dev/null
    Affected if Version or build number is returned from the app bundle
  3. Compare against fixed builds
    Compare your build number to 41396 (standard) or 42571 (OEM). If you cannot determine OEM vs standard, treat the higher threshold (42571) as the safe threshold.
    Affected if Installed build number is less than 41396 (standard) or less than 42571 (OEM), or build number cannot be determined but version is older than the fixed releases
  4. Check if Acronis service/process is active
    Run: ps aux | grep -i 'Acronis' | grep -v grep. Also check for running helper/agent processes in Activity Monitor.
    Affected if Acronis True Image daemon, helper, or agent process is running on the system

If Acronis True Image for macOS is installed with a build number below 41396 (or below 42571 for OEM versions), the system is potentially vulnerable to local privilege escalation via this CVE.

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 True Image to build 41396 or later (standard version) or build 42571 or later (OEM version).

Recommended fix Moderate confidence

Acronis True Image (macOS) build 41396 or later; Acronis True Image OEM (macOS) build 42571 or later

  1. Upgrade Acronis True Image (macOS) to build 41396 or later
  2. Upgrade Acronis True Image OEM (macOS) to build 42571 or later
  3. After upgrade, verify the installed version matches or exceeds the fixed build number

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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