# CVE-2021-3845: External Control of File Name or Path in netristv/ws-scrcpy

> Attackers can manipulate file paths to read or modify arbitrary files in the ws-scrcpy web application.

- **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:** 4 Jan 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-rrcw-m6cc-w2cx

## What is CVE-2021-3845?

CVE-2021-3845 is a high-severity path traversal vulnerability in netristv/ws-scrcpy, published on 4 Jan 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ws-scrcpy is vulnerable to External Control of File Name or Path

Weakness: CWE-610 (Externally Controlled Reference to a Resource in Another Sphere), CWE-73 (External Control of File Name or Path)

## Which versions are affected by CVE-2021-3845?

It affects 1 product.


Products: Ws Scrcpy Project Ws Scrcpy.

## How do I fix CVE-2021-3845?

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

## Is CVE-2021-3845 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-3845 and fix it if it is affected.

What it is: CVE-2021-3845 is a high-severity path traversal vulnerability in netristv/ws-scrcpy, published on 4 Jan 2022. 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-2021-3845 in the wild and no public exploit code.

Affected product: netristv/ws-scrcpy. 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-2021-3845/ (Markdown: https://insights.sbomify.com/CVE-2021-3845/index.md)
```

## Sources

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

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