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

> A timing side-channel in Crypto++ ECDSA signature generation allows attackers to recover private keys by measuring operation durations.

- **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:** Yes
- **Published:** 30 Jul 2019
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2019-14318, GHSA-j77v-9g36-cfp2, MGASA-2019-0362, UBUNTU-CVE-2019-14318, openSUSE-SU-2019:1968-1

## What is CVE-2019-14318?

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

### Official description

Crypto++ 8.3.0 and earlier contains a timing side channel in ECDSA signature generation. This allows a local or remote attacker, able to measure the duration of hundreds to thousands of signing operations, to compute the private key used. The issue occurs because scalar multiplication in ecp.cpp (prime field curves, small leakage) and algebra.cpp (binary field curves, large leakage) is not constant time and leaks the bit length of the scalar among other information.

Weakness: CWE-417

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `libcryptopp` | SUSE:Package Hub 15 | All versions | 5.6.5-bp151.4.3.1 |
| `libcryptopp` | SUSE:Package Hub 15 SP1 | All versions | 5.6.5-bp151.4.3.1 |
| `libcryptopp` | openSUSE:Leap 15.0 | All versions | 5.6.5-bp151.4.3.1 |
| `libcryptopp` | openSUSE:Leap 15.1 | All versions | 5.6.5-bp151.4.3.1 |

Products: Cryptopp Crypto\+\+.

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

Upgrade to a fixed version.

## Is CVE-2019-14318 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-50980](https://insights.sbomify.com/CVE-2023-50980/): Denial of service in n/a (high 7.5)
- [CVE-2023-50981](https://insights.sbomify.com/CVE-2023-50981/): Denial of service in n/a (high 7.5)
- [CVE-2022-48570](https://insights.sbomify.com/CVE-2022-48570/): Information disclosure in n/a (high 7.5)
- [CVE-2016-3995](https://insights.sbomify.com/CVE-2016-3995/): Information disclosure in n/a (high 7.5)
- [CVE-2016-7544](https://insights.sbomify.com/CVE-2016-7544/): Use after free in n/a (high 7.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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