← Back

Wolfssl

wolfssl

Vendor: Wolfssl • 151 CVEs

CVEs (151)

CVE
VENDORS
PRODUCTS
UPDATED
PUBLISHED
CVSS
3Arubanetworks
SiemensWolfssl
3Instant
Scalance W1750d FirmwareWolfssl
May 13, 2026
Dec 13, 2017
N/A· v4
5.9 MEDIUM· v3
4.3 MEDIUM· v2
wolfSSL prior to version 3.12.2 provides a weak Bleichenbacher oracle when any TLS cipher suite using RSA key exchange is negotiated. An attacker can recover the private key from a vulnerable wolfSSL application. This vu...Show more
wolfSSL prior to version 3.12.2 provides a weak Bleichenbacher oracle when any TLS cipher suite using RSA key exchange is negotiated. An attacker can recover the private key from a vulnerable wolfSSL application. This vulnerability is referred to as "ROBOT."Show less
1Wolfssl
1Wolfssl
May 13, 2026
Oct 6, 2017
N/A· v4
5.9 MEDIUM· v3
4.3 MEDIUM· v2
CyaSSL does not check the key usage extension in leaf certificates, which allows remote attackers to spoof servers via a crafted server certificate not authorized for use in an SSL/TLS handshake.
1Wolfssl
1Wolfssl
May 13, 2026
May 24, 2017
N/A· v4
9.8 CRITICAL· v3
7.5 HIGH· v2
A specially crafted x509 certificate can cause a single out of bounds byte overwrite in wolfSSL through 3.10.2 resulting in potential certificate validation vulnerabilities, denial of service and possible remote code exe...Show more
A specially crafted x509 certificate can cause a single out of bounds byte overwrite in wolfSSL through 3.10.2 resulting in potential certificate validation vulnerabilities, denial of service and possible remote code execution. In order to trigger this vulnerability, the attacker needs to supply a malicious x509 certificate to either a server or a client application using this library.Show less
1Wolfssl
1Wolfssl
May 13, 2026
May 9, 2017
N/A· v4
7.5 HIGH· v3
5.0 MEDIUM· v2
wolfSSL before 3.11.0 does not prevent wc_DhAgree from accepting a malformed DH key.
1Wolfssl
1Wolfssl
May 13, 2026
May 9, 2017
N/A· v4
7.8 HIGH· v3
6.8 MEDIUM· v2
wolfSSL before 3.10.2 has an out-of-bounds memory access with loading crafted DH parameters, aka a buffer overflow triggered by a malformed temporary DH file.
1Wolfssl
1Wolfssl
May 13, 2026
Feb 24, 2017
N/A· v4
5.5 MEDIUM· v3
2.1 LOW· v2
In versions of wolfSSL before 3.10.2 the function fp_mul_comba makes it easier to extract RSA key information for a malicious user who has access to view cache on a machine.
4Debian
MariadbOracle+1 more
4Debian Linux
MariadbMysql+1 more
May 6, 2026
Dec 13, 2016
N/A· v4
5.5 MEDIUM· v3
2.1 LOW· v2
The C software implementation of AES Encryption and Decryption in wolfSSL (formerly CyaSSL) before 3.9.10 makes it easier for local users to discover AES keys by leveraging cache-bank timing differences.
1Wolfssl
1Wolfssl
May 6, 2026
Dec 13, 2016
N/A· v4
5.5 MEDIUM· v3
2.1 LOW· v2
The C software implementation of RSA in wolfSSL (formerly CyaSSL) before 3.9.10 makes it easier for local users to discover RSA keys by leveraging cache-bank hit differences.
1Wolfssl
1Wolfssl
May 6, 2026
Dec 13, 2016
N/A· v4
5.5 MEDIUM· v3
2.1 LOW· v2
The C software implementation of ECC in wolfSSL (formerly CyaSSL) before 3.9.10 makes it easier for local users to discover RSA keys by leveraging cache-bank hit differences.
3Mariadb
OpensuseWolfssl
4Leap
MariadbOpensuse+1 more
May 6, 2026
Jan 22, 2016
N/A· v4
5.9 MEDIUM· v3
2.6 LOW· v2
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...Show more
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.Show less
1Wolfssl
1Wolfssl
May 6, 2026
Jan 22, 2016
N/A· v4
7.5 HIGH· v3
5.0 MEDIUM· v2
wolfSSL (formerly CyaSSL) before 3.6.8 allows remote attackers to cause a denial of service (resource consumption or traffic amplification) via a crafted DTLS cookie in a ClientHello message.