# CVE-2020-6852: Auth bypass in n/a

> Weak TELNET authentication allows attackers to gain root privileges without a password on CACAGOO Cloud Storage Intelligent Cameras.

- **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:** 2 Apr 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-wwjx-6rfc-2qjh

## What is CVE-2020-6852?

CVE-2020-6852 is a critical authentication bypass vulnerability in n/a, published on 2 Apr 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

CACAGOO Cloud Storage Intelligent Camera TV-288ZD-2MP with firmware 3.4.2.0919 has weak authentication of TELNET access, leading to root privileges without any password required.

Weakness: CWE-307 (Improper Restriction of Excessive Authentication Attempts)

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

It affects 1 product.


Products: Cacagoo Tv-288zd-2mp Firmware.

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

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

## Is CVE-2020-6852 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-9349](https://insights.sbomify.com/CVE-2020-9349/): Auth bypass in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-6852 is a critical authentication bypass vulnerability in n/a, published on 2 Apr 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-6852 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-6852/ (Markdown: https://insights.sbomify.com/CVE-2020-6852/index.md)
```

## Sources

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

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