Skip to content
Fencer Intel
medium 5.9

CVE-2019-14318 json

Crypto++ 8.3.0 and earlier contains a timing side channel in ECDSA signature generation.

published 7y ago modified 4mo ago also EUVD-2019-5542

cvss
5.9
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
3.1%
EPSS 3.1% chance of exploitation in 30 days, percentile 87%
public exploits
0
none known

Summary

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.

Patch / fix

  • libcrypto++ Debian 14, Debian 13, Debian 12 5.6.4-9

debian advisories DEBIAN-CVE-2019-14318

  • libcryptopp openSUSE Tumbleweed 8.6.0-1.1
  • libcryptopp Package Hub 15 SP1, Package Hub 15, openSUSE Leap 15.1 +1 more 5.6.5-bp151.4.3.1

opensuse advisories openSUSE-SU-2024:10933-1openSUSE-SU-2019:1968-1

  • crypto++ Arch Linux 8.2.0-2

arch linux advisories AVG-1046

Is CVE-2019-14318 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

3.10% chance of exploitation in the next 30 days, higher than 87% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • eprint.iacr.org https://eprint.iacr.org/2011/232.pdf referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.0 5.9 CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:P/I:N/A:N

Classification

Weakness
  • CWE-417 Communication Channel Errors

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.