dbcve.org
AgentApplication · Acronis

CVE-2020-14999

HIGH · 7.5 CVSS v3.1 Published 2021-07-30
Fix available
A fix is available. Upgrade to after 12.5.23094 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
A logic bug in system monitoring driver of Acronis Agent after 12.5.21540 and before 12.5.23094 allowed to bypass Windows memory protection and access sensitive data.

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 logic bug in the Acronis Agent system monitoring driver allows bypassing Windows memory protection mechanisms to access sensitive data, representing a security bypass vulnerability.

MitigationUpgrade Acronis Agent to version 12.5.23094 or later to remediate the logic bug in the system monitoring driver.

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
AgentApplication
Affected:>= 12.5.21540, <= 12.5.23094

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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 Agent is installed
    Check for Acronis Agent installation by looking in Program Files for the Acronis folder, or check Windows Services for 'Acronis Agent' or 'Acronis Managed Machine Service'
    Affected if Acronis Agent is not installed on the system
  2. Determine installed Acronis Agent version
    Open Windows Control Panel > Programs and Features, find Acronis Agent, and note the version number shown in the Version column
    Affected if Version number falls within range >= 12.5.21540 and <= 12.5.23094
  3. Check system monitoring driver presence
    Open Windows Device Manager, expand 'System devices' or look for a driver named 'Acronis System Monitoring' or similar Acronis driver component
    Affected if The Acronis system monitoring driver is present and loaded on the system
  4. Verify service configuration
    Open Services console (services.msc), locate the Acronis Agent service, check the 'Path to executable' to confirm it points to the affected version location
    Affected if Service executable path corresponds to a version in the affected range

The system is affected if Acronis Agent is installed with a version between 12.5.21540 and 12.5.23094 inclusive, and the system monitoring driver component is present.

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
Upgrade available Upgrade to a release after 12.5.23094
Interim mitigation

Upgrade Acronis Agent to version 12.5.23094 or later to remediate the logic bug in the system monitoring driver.

Fix this in Agent Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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