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

> Hardcoded RSA keys in Cellebrite UFED allow attackers to bypass authentication and modify evidence on target devices during forensic extraction.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Apr 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-2p37-pq7q-44mr

## What is CVE-2020-11723?

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

### Official description

Cellebrite UFED 5.0 through 7.29 uses four hardcoded RSA private keys to authenticate to the ADB daemon on target devices. Extracted keys can be used to place evidence onto target devices when performing a forensic extraction.

Weakness: CWE-798 (Use of Hard-coded Credentials)

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

It affects 1 product.


Products: Cellebrite Ufed Firmware.

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

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

## Is CVE-2020-11723 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-14474](https://insights.sbomify.com/CVE-2020-14474/): Hardcoded credentials in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-11723 is a medium-severity vulnerability in n/a, published on 14 Apr 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-11723 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-11723/ (Markdown: https://insights.sbomify.com/CVE-2020-11723/index.md)
```

## Sources

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

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