# CVE-2020-29001: Hardcoded credentials in n/a

> Remote attackers can take full control of Geeni and Merkury cameras and doorbells using static credentials compiled into the firmware.

- **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-3qgj-r7gq-79qf

## What is CVE-2020-29001?

CVE-2020-29001 is a high-severity 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-CW028 Camera 2.7.2, Geeni GNC-CW025 Doorbell 2.9.5, Merkury MI-CW024 Doorbell 2.9.6, and Merkury MI-CW017 Camera 2.9.6 devices. A vulnerability exists in the RESTful Services API that allows a remote attacker to take full control of the camera with a high-privileged account. The vulnerability exists because a static username and password are compiled into the ppsapp RESTful application.

Weakness: CWE-312 (Cleartext Storage of Sensitive Information)

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

It affects 4 products.


Products: Merkuryinnovations Geeni Gnc-Cw025 Firmware, Merkuryinnovations Geeni Gnc-Cw028 Firmware, Merkuryinnovations Merkury Mi-Cw017 Firmware, Merkuryinnovations Merkury Mi-Cw024 Firmware.

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

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

## Is CVE-2020-29001 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-29001 is a high-severity 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-29001 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-29001/ (Markdown: https://insights.sbomify.com/CVE-2020-29001/index.md)
```

## Sources

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

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