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

> An attacker can exploit a directory traversal flaw in libslirp's TFTP implementation on Windows to read or modify arbitrary files.

- **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:** Yes
- **Published:** 21 Jan 2020
- **Updated:** 4 Aug 2024
- **Also known as:** DEBIAN-CVE-2020-7211, GHSA-g6ww-98w5-h2gm

## What is CVE-2020-7211?

CVE-2020-7211 is a high-severity path traversal vulnerability in Qemu Qemu, published on 21 Jan 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

tftp.c in libslirp 4.1.0, as used in QEMU 4.2.0, does not prevent ..\ directory traversal on Windows.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 2 products.


Products: Libslirp Project Libslirp, Qemu Qemu.

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

Upgrade to a fixed version.

## Is CVE-2020-7211 being exploited?

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

## Other vulnerabilities in Qemu Qemu

- [CVE-2019-14378](https://insights.sbomify.com/CVE-2019-14378/): Memory corruption in n/a (high 8.8)
- [CVE-2019-15890](https://insights.sbomify.com/CVE-2019-15890/): Use after free in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-7211 is a high-severity path traversal vulnerability in Qemu Qemu, published on 21 Jan 2020. 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-7211 in the wild and no public exploit code.

Affected product: Qemu Qemu. 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-7211/ (Markdown: https://insights.sbomify.com/CVE-2020-7211/index.md)
```

## Sources

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

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