Skip to content
Fencer Intel
low 1.9

CVE-2014-0076 json

The Montgomery ladder implementation in OpenSSL through 1.0.0l does not ensure that certain swap operations have a constant-time behavior,…

published 2014-03-25 12 y ago modified 2026-06-17 4 mo ago also EUVD-2014-0168

cvss
1.9
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.8%
EPSS 0.8% chance of exploitation in 30 days, percentile 58%
public exploits
0
none known

Summary

The Montgomery ladder implementation in OpenSSL through 1.0.0l does not ensure that certain swap operations have a constant-time behavior, which makes it easier for local users to obtain ECDSA nonces via a FLUSH+RELOAD cache side-channel attack.

Patch / fix

  • openssl Debian 14, Debian 13, Debian 12 1.0.1g-1

debian advisories DEBIAN-CVE-2014-0076

  • libqt4 SLES 12 SP1, SLES 12, SLED 12 SP1 +7 more 4.8.6-7.1
  • libqt4-sql-plugins SLES 12 SP1, SLES 12, SLED 12 SP1 +7 more 4.8.6-7.1

suse advisories SUSE-SU-403SUSE-SU-403 Forbidden-1

  • openssl-1_1 openSUSE Tumbleweed 1.1.1l-1.2

opensuse advisories openSUSE-SU-2024:11127-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2014-0076 updated cvss 4.3

openssl: ECDSA nonces susceptible to Yarom/Benger flush+reload cache side-channel attack

  • Red Hat Enterprise Linux 5 openssl, openssl097a Red Hat Enterprise Linux 6 openssl, openssl098e, openssl-perl Red Hat Enterprise Linux 7 openssl, openssl098e, openssl-libs, openssl-perl
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

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

CVSS scores

assigned by version score vector
NVD 2.0 1.9 AV:L/AC:M/Au:N/C:P/I:N/A:N

Classification

Weakness
Technology feeds

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.