Skip to content
Fencer Intel
medium 5.9

CVE-2015-7744 json

wolfSSL (formerly CyaSSL) before 3.6.8 does not properly handle faults associated with the Chinese Remainder Theorem (CRT) process when all…

published 2016-01-22 10 y ago modified 2026-06-17 4 mo ago also EUVD-2015-7644

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

Summary

wolfSSL (formerly CyaSSL) before 3.6.8 does not properly handle faults associated with the Chinese Remainder Theorem (CRT) process when allowing ephemeral key exchange without low memory optimizations on a server, which makes it easier for remote attackers to obtain private RSA keys by capturing TLS handshakes, aka a Lenstra attack.

Patch / fix

  • wolfssl wolfssl 3.6.8
  • mariadb mariadb 5.5.46, 10.0.22, 10.1.9
  • wolfssl Debian 13, Debian 12 3.9.10+dfsg-1

debian advisories DEBIAN-CVE-2015-7744

  • mysql-5.5 Ubuntu 14.04 LTS 5.5.46-0ubuntu0.14.04.2
  • mysql-5.6 Ubuntu 14.04 LTS 5.6.27-0ubuntu0.14.04.1
  • mariadb-5.5 Ubuntu 14.04 LTS 5.5.46-1ubuntu0.14.04.2
  • percona-xtradb-cluster-5.6 Ubuntu 16.04 LTS 5.6.34-26.19-0ubuntu0.16.04.1

ubuntu advisories UBUNTU-CVE-2015-7744

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • mariadb104 SLES for SAP 12 SP5, SLES 12 SP5, SLE Software Development Kit 12 SP5 10.4.30-8.5.46
  • lz4 SLES for SAP 12 SP5, SLES 12 SP5, SLE Software Development Kit 12 SP5 1.8.0-3.5.2
  • python-mysqlclient SLES for SAP 12 SP5, SLES 12 SP5, SLE Software Development Kit 12 SP5 1.3.14-8.9.2
  • mariadb-connector-c SLES for SAP 12 SP5, SLES 12 SP5, SLE Software Development Kit 12 SP5 3.1.22-2.35.1
  • mysql SLES for SAP 11 SP4, SLES for SAP 11 SP3, SLES 11 SP4 +6 more 5.5.47-0.17.1
  • mariadb104 SLES for SAP 15 SP1, SLES 15 SP1-LTSS, SLE High Performance Computing 15 SP1-LTSS 10.4.30-150100.3.5.10
  • python-mysqlclient SLES for SAP 15 SP1, SLES 15 SP1-LTSS, SLE High Performance Computing 15 SP1-LTSS 1.4.6-150100.3.3.7

suse advisories SUSE-RU-2023:4991-1SUSE-RU-2023:3956-1SUSE-SU-2016:0348-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-2015-7744 updated cvss 2.6

wolfSSL: insufficient hardening of RSA-CRT implementation (Oracle MySQL CPU Jan 2016)

  • Red Hat Enterprise Linux 5 mysql55-mysql Red Hat Enterprise Linux 6 mysql, mysql-libs, mysql-test, mysql-bench, mysql-server, mysql-embedded Red Hat Enterprise Linux 7 mariadb, mariadb-libs, mariadb-test, mariadb-bench, mariadb-server, mariadb-embedded Red Hat Enterprise Linux OpenStack Platform 5 (Icehouse) mariadb-galera Red Hat Enterprise Linux OpenStack Platform 6 (Juno) mariadb-galera Red Hat Enterprise Linux OpenStack Platform 7 (Kilo) mariadb-galera, mariadb-galera-common, mariadb-galera-server
    +1 more products
    Red Hat Software Collections mysql55-mysql, rh-mysql56-mysql, mariadb55-mariadb, mysql55-mysql-libs, mysql55-mysql-test, mysql55-mysql-bench, +19 more
    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

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

Exploits and checks

  • people.redhat.com https://people.redhat.com/~fweimer/rsa-crt-leaks.pdf referenced PoC, tagged "exploit" by a source, unverified
  • securityblog.redhat.com https://securityblog.redhat.com/2015/09/02/factoring-rsa-keys-with-tls-perfect-forward-secrecy/ referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

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

Classification

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.