# CVE-2022-41505: Auth bypass in n/a

> Physically proximate attackers can gain root access on TP-Link Tapo C200 cameras by interrupting the boot process via UART pins.

- **Severity:** Medium 6.4 (`CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Jan 2023
- **Updated:** 3 Apr 2025
- **Also known as:** GHSA-79vq-pg3g-r563

## What is CVE-2022-41505?

CVE-2022-41505 is a medium-severity authentication bypass vulnerability in n/a, published on 23 Jan 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An access control issue on TP-LInk Tapo C200 V1 devices allows physically proximate attackers to obtain root access by connecting to the UART pins, interrupting the boot process, and setting an init=/bin/sh value.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2022-41505?

It affects 1 product.


Products: Tp-Link Tapo C200 V1 Firmware.

## How do I fix CVE-2022-41505?

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

## Is CVE-2022-41505 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-41505 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-41505 and fix it if it is affected.

What it is: CVE-2022-41505 is a medium-severity authentication bypass vulnerability in n/a, published on 23 Jan 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-41505 exists.

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-2022-41505/ (Markdown: https://insights.sbomify.com/CVE-2022-41505/index.md)
```

## Sources

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

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