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

> Remote attackers can bypass authentication to gain full control of Geeni smart doorbells via a crafted RTSP message, enabling telnet access.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Jan 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-23g2-95w8-rx32

## What is CVE-2020-29000?

CVE-2020-29000 is a high-severity authentication bypass vulnerability in n/a, published on 26 Jan 2021. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

An issue was discovered on Geeni GNC-CW013 doorbell 1.8.1 devices. A vulnerability exists in the RTSP service that allows a remote attacker to take full control of the device with a high-privileged account. By sending a crafted message, an attacker is able to remotely deliver a telnet session. Any attacker that has the ability to control DNS can exploit this vulnerability to remotely login to the device and gain access to the camera system.

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

It affects 1 product.


Products: Mygeeni Gnc-Cw013 Firmware.

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

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

## Is CVE-2020-29000 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-28998](https://insights.sbomify.com/CVE-2020-28998/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2020-28999](https://insights.sbomify.com/CVE-2020-28999/): Hardcoded credentials in n/a (high 7.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-29000 is a high-severity authentication bypass vulnerability in n/a, published on 26 Jan 2021. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-29000 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-29000/ (Markdown: https://insights.sbomify.com/CVE-2020-29000/index.md)
```

## Sources

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

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