# CVE-2020-14999: Security feature bypass in n/a

> A logic bug in the Acronis Agent monitoring driver allows bypassing Windows memory protection to access sensitive data.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Jul 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-pvm4-qq6f-fmrw

## What is CVE-2020-14999?

CVE-2020-14999 is a high-severity vulnerability in n/a, published on 27 Jul 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

## Which versions are affected by CVE-2020-14999?

It affects 1 product.


Products: Acronis Agent.

## How do I fix CVE-2020-14999?

No fix has been published for CVE-2020-14999 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-14999 being exploited?

There is no known exploitation of CVE-2020-14999 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2022-45451](https://insights.sbomify.com/CVE-2022-45451/): Privilege escalation in Acronis Agent (high 8.8)
- [CVE-2023-41743](https://insights.sbomify.com/CVE-2023-41743/): Privilege escalation in Acronis Cyber Protect 15 (high 8.8)
- [CVE-2026-28727](https://insights.sbomify.com/CVE-2026-28727/): Privilege escalation in Acronis Cyber Protect 17 (high 7.8)
- [CVE-2023-41744](https://insights.sbomify.com/CVE-2023-41744/): Privilege escalation in Acronis Agent (high 7.8)
- [CVE-2021-44204](https://insights.sbomify.com/CVE-2021-44204/): Local privilege escalation via named pipe due to improper access control checks (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-14999 and fix it if it is affected.

What it is: CVE-2020-14999 is a high-severity vulnerability in n/a, published on 27 Jul 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-14999 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-14999/ (Markdown: https://insights.sbomify.com/CVE-2020-14999/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-14999
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-14999
- OSV: https://osv.dev/vulnerability/CVE-2020-14999

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-14999/
Summaries are generated and may contain mistakes; the official description above is the record.