# CVE-2019-14357: Information disclosure in n/a

> A power side-channel in the OLED display allows partial recovery of displayed secrets like PINs if an attacker controls the USB connection.

- **Severity:** Low 2.4 (`CVSS:3.0/AV:P/AC:L/PR:N/UI:N/S:U/C:L/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:** 10 Aug 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-3742-g66h-97pc

## What is CVE-2019-14357?

CVE-2019-14357 is a low-severity vulnerability in n/a, published on 10 Aug 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

On Mooltipass Mini devices, a side channel for the row-based OLED display was found. The power consumption of each row-based display cycle depends on the number of illuminated pixels, allowing a partial recovery of display contents. For example, a hardware implant in the USB cable might be able to leverage this behavior to recover confidential secrets such as the PIN. In other words, the side channel is relevant only if the attacker has enough control over the device's USB connection to make power-consumption measurements at a time when secret data is displayed. The side channel is not relevant in other circumstances, such as a stolen device that is not currently displaying secret data. NOTE: the vendor's position is that an attack is not "realistically implementable.

Weakness: CWE-203 (Observable Discrepancy)

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

It affects 1 product.


Products: Mooltipass Mooltipass Mini Firmware.

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

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

## Is CVE-2019-14357 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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