# CVE-2019-12813: Weak cryptography in n/a

> An attacker can decrypt fingerprint images by sniffing cleartext keys and salts during transfer to the driver, compromising biometric data.

- **Severity:** Medium 5.9 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Jun 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-q63x-55rg-p2jm

## What is CVE-2019-12813?

CVE-2019-12813 is a medium-severity vulnerability in n/a, published on 13 Jun 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in Digital Persona U.are.U 4500 Fingerprint Reader v24. The key and salt used for obfuscating the fingerprint image exhibit cleartext when the fingerprint scanner device transfers a fingerprint image to the driver. An attacker who sniffs an encrypted fingerprint image can easily decrypt that image using the key and salt.

Weakness: CWE-319 (Cleartext Transmission of Sensitive Information)

## Which versions are affected by CVE-2019-12813?

It affects 1 product.


Products: Crossmatch Digital Persona U.are.u 4500 Firmware.

## How do I fix CVE-2019-12813?

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

## Is CVE-2019-12813 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-12813 and fix it if it is affected.

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

## Sources

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

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