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

> An attacker with physical access can bypass authentication using a hardcoded backdoor password to access stored credentials.

- **Severity:** Medium 4.6 (`CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **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:** 30 Nov 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-4jhh-wmhx-r4j7

## What is CVE-2020-29392?

CVE-2020-29392 is a medium-severity vulnerability in n/a, published on 30 Nov 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The Estil Hill Lock Password Manager Safe app 2.3 for iOS has a *#06#* backdoor password. An attacker with physical access can unlock the password manager without knowing the master password set by the user.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Lock Password Manager Safe App Project Lock Password Manager Safe App.

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

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

## Is CVE-2020-29392 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-29392 is a medium-severity vulnerability in n/a, published on 30 Nov 2020. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-29392 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-29392/ (Markdown: https://insights.sbomify.com/CVE-2020-29392/index.md)
```

## Sources

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

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