# CVE-2020-11443: Path traversal in n/a

> A local attacker can exploit symbolic links in the Zoom installer to delete arbitrary files with SYSTEM privileges, potentially leading to privilege escalation or denial of service.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 May 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-wc6m-2q93-p5qr

## What is CVE-2020-11443?

CVE-2020-11443 is a high-severity path traversal vulnerability in n/a, published on 4 May 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Zoom IT installer for Windows (ZoomInstallerFull.msi) prior to version 4.6.10 deletes files located in %APPDATA%\Zoom before installing an updated version of the client. Standard users are able to write to this directory, and can write links to other directories on the machine. As the installer runs with SYSTEM privileges and follows these links, a user can cause the installer to delete files that otherwise cannot be deleted by the user.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource), CWE-59 (Improper Link Resolution Before File Access)

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

It affects 1 product.


Products: Zoom It Installer.

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

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

## Is CVE-2020-11443 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-11443 is a high-severity path traversal vulnerability in n/a, published on 4 May 2020. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-11443 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-11443/ (Markdown: https://insights.sbomify.com/CVE-2020-11443/index.md)
```

## Sources

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

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