# CVE-2020-27614: Privilege escalation in n/a

> Local attackers can exploit improper XPC request validation in AnyDesk for macOS to escalate privileges.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Dec 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-f534-wv46-r4jg

## What is CVE-2020-27614?

CVE-2020-27614 is a high-severity vulnerability in n/a, published on 9 Dec 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

AnyDesk for macOS versions 6.0.2 and older have a vulnerability in the XPC interface that does not properly validate client requests and allows local privilege escalation.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Anydesk Anydesk.

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

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

## Is CVE-2020-27614 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-27918](https://insights.sbomify.com/CVE-2025-27918/): Integer overflow in n/a (critical 9.8)
- [CVE-2020-13160](https://insights.sbomify.com/CVE-2020-13160/): Other in n/a (critical 9.8)
- [CVE-2017-14397](https://insights.sbomify.com/CVE-2017-14397/): AnyDesk before 3.6.1 on Windows has a DLL injection vulnerability. (critical 9.8)
- [CVE-2021-44426](https://insights.sbomify.com/CVE-2021-44426/): File upload in n/a (high 8.8)
- [CVE-2016-20094](https://insights.sbomify.com/CVE-2016-20094/): AnyDesk 2.5.0 Unquoted Service Path Elevation of Privilege (high 8.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-27614 is a high-severity vulnerability in n/a, published on 9 Dec 2020. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-27614 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-27614/ (Markdown: https://insights.sbomify.com/CVE-2020-27614/index.md)
```

## Sources

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

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