Skip to content
Fencer Intel
medium 4.7

CVE-2019-18222 json

The ECDSA signature implementation in ecdsa.c in Arm Mbed Crypto 2.1 and Mbed TLS through 2.19.1...

published 6y ago modified 3mo ago also EUVD-2019-8022 , JLSEC-2025-199

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

Summary

The ECDSA signature implementation in ecdsa.c in Arm Mbed Crypto 2.1 and Mbed TLS through 2.19.1 does not reduce the blinded scalar before computing the inverse, which allows a local attacker to recover the private key via side-channel attacks.

Patch / fix

  • julia MbedTLS_jll 2.16.6+0
  • arm mbed_crypto 3.0.0
  • arm mbed_tls 2.7.13, 2.16.4, 2.20.0
  • mbedtls Debian 14, Debian 13, Debian 12 2.16.4-1

debian advisories DEBIAN-CVE-2019-18222

  • mbedtls Alpine 3.24, Alpine 3.23, Alpine 3.22 +12 more 2.16.4-r0
  • mbedtls2 Alpine 3.24, Alpine 3.23, Alpine 3.22 +2 more 2.16.4-r0
  • mbedtls3 Alpine 3.24 2.16.4-r0

alpine advisories ALPINE-CVE-2019-18222

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • mbedtls Arch Linux 2.16.5-1

arch linux advisories AVG-1104

Is CVE-2019-18222 in your dependencies? 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

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

CVSS scores

assigned by version score vector
NVD 3.1 4.7 CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N
NVD 2.0 1.9 AV:L/AC:M/Au:N/C:P/I:N/A:N
OSV 3.1 4.7 CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
julia MbedTLS_jll
<2.16.6+0
2.16.6+0

Classification

Weakness

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.