# CVE-2021-4045: TP-LINK Tapo C200 remote code execution vulnerability

> Unauthenticated attackers can execute arbitrary commands on TP-Link Tapo C200 cameras via the uhttpd binary, gaining full control.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Mar 2022
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-574v-3xxh-gwh5

## What is CVE-2021-4045?

CVE-2021-4045 is a critical command injection vulnerability in TP-Link Tapo C200, published on 7 Mar 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

TP-Link Tapo C200 IP camera, on its 1.1.15 firmware version and below, is affected by an unauthenticated RCE vulnerability, present in the uhttpd binary running by default as root. The exploitation of this vulnerability allows an attacker to take full control of the camera.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command)

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

It affects 1 product.


Products: Tp-Link Tapo C200 Firmware.

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

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

## Is CVE-2021-4045 being exploited?

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

Public exploit code:

- Exploit for command injection vulnerability found in uhttpd binary from TP-Link Tapo c200 IP camera (github_poc): https://github.com/hacefresko/CVE-2021-4045
- 🔐 "PWNTAPO: Unveiling Command Injection in TP-Link Tapo C200 Cameras (<= v1.1.16 Build 211209)" 🔓 (github_poc): https://github.com/0xbinder/CVE-2021-4045
- CVE-2021-4045 CVE-2021-4045 is a Command Injection vulnerability that allows Remote Code Execution in the TP-Link Tapo c200 IP camera. It affects all firmware versions prior to 1.1.16 Build 211209 Rel. 37726N due to insufficient checks on user input in uhttpd, which is one of the main binaries of the device. (github_poc): https://github.com/234329a423853/CVE-2021-4045
- TP-Link Tapo c200 ver <1.1.15 - Remote Code Execution (RCE) (github_poc): https://github.com/jeffbezosispogg/CVE-2021-4045
- Sets up a local Tapo C200 using CVE-2021-4045 (github_poc): https://github.com/DorskFR/tapodate
- TP-Link Tapo c200 1.1.15 - Remote Code Execution (RCE) (exploitdb)

## Other vulnerabilities in TP-Link Tapo C200

- [CVE-2025-14300](https://insights.sbomify.com/CVE-2025-14300/): Unauthenticated Access to connectAP API Endpoint on Tapo C100, C200 & C425 (high 8.7)
- [CVE-2025-8065](https://insights.sbomify.com/CVE-2025-8065/): Remote Code Execution via Stack-based Buffer Overflow in ONVIF SOAP Parser in TP-Link Tapo C200 and C520WS (high 8.7)
- [CVE-2026-15316](https://insights.sbomify.com/CVE-2026-15316/): Denial-of-Service via Oversized Encrypted Credential Input in TP-Link Tapo C200 (high 7.1)
- [CVE-2026-12760](https://insights.sbomify.com/CVE-2026-12760/): Denial-of-Service Vulnerability via Malformed IPv4 Fragmentation Handling in TP-Link Tapo C200 (high 7.1)
- [CVE-2026-1871](https://insights.sbomify.com/CVE-2026-1871/): Authenticated Stack-based Buffer Overflow in RTSP Authentication of Tapo C200 (high 7.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-4045 is a critical command injection vulnerability in TP-Link Tapo C200, published on 7 Mar 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-4045 in the wild and no public exploit code.

Affected product: TP-Link Tapo C200. 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-4045/ (Markdown: https://insights.sbomify.com/CVE-2021-4045/index.md)
```

## Sources

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

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