Wolfssl vulnerabilitiesNone on the known-exploited list.
Wolfssl has 66 published vulnerabilities across 4 products in our catalogue. None of them is on the list of flaws known to be exploited today. The most affected product is Wolfssl, with 58. If you run Wolfssl software, patch the exploited flaws first.
We keep watching the known-exploited list.
Which Wolfssl vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Wolfssl's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Wolfssl flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 27%CVE-2017-13099High
wolfSSL prior to version 3.12.2 provides a weak Bleichenbacher oracle when any TLS cipher suite using RSA key exchange is negotiated.
- 9.2%CVE-2019-11873Critical
wolfSSL 4.0.0 has a Buffer Overflow in DoPreSharedKeys in tls13.c when a current identity size is greater than a client identity size.
- 8.5%CVE-2017-2800Critical
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...
- 5.8%CVE-2022-39173High
In wolfSSL before 5.5.1, malicious clients can cause a buffer overflow during a TLS 1.3 handshake.
- 5.0%CVE-2015-7744Medium
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,...
- 3.6%CVE-2020-36177Critical
RsaPad_PSS in wolfcrypt/src/rsa.c in wolfSSL before 4.6.0 has an out-of-bounds write for certain relationships between key size and digest size.
- 3.0%CVE-2015-6925High
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.
- 2.8%CVE-2014-2897Critical
The SSL 3 HMAC functionality in wolfSSL CyaSSL 2.5.0 before 2.9.4 does not check the padding length when verification fails, which allows remote attackers to have unspecified impact via a crafted HMAC, which triggers...
- 2.8%CVE-2014-2898Critical
wolfSSL CyaSSL before 2.9.4 allows remote attackers to have unspecified impact via multiple calls to the CyaSSL_read function which triggers an out-of-bounds read when an error occurs, related to not checking the...
All Wolfssl products we track.
3 products, most vulnerabilities first. Find the ones you run, then open a product to see its versions and exploited flaws.
- Wolfsslwolfssl58 vulnerabilities114 versions
- Wolfmqttwolfmqtt7 vulnerabilities23 versions
- Yasslyassl1 vulnerability58 versions
This directory lists the 3 Wolfssl products with at least one tracked version, of 4 in our catalogue.
Running Wolfssl? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
Multiple stack-based buffer overflows in the CertDecoder::GetName function in src/asn.cpp in TaoCrypt in yaSSL before 1.9.9, as used in mysqld in MySQL 5.0.x before 5.0.90, MySQL 5.1.x before 5.1.43, MySQL 5.5.x through 5.5.0-m2, and other products, allow remote attackers to execute arbitrary code or cause a denial of service (memory corruption and daemon crash) by establishing an SSL connection and sending an X.509 client certificate with a crafted name field, as demonstrated by mysql_overflow1.py and the vd_mysql5 module in VulnDisco Pack Professional 8.11. NOTE: this was originally reported for MySQL 5.0.51a.
- Matched to
- Yassl on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
Our catalogue lists 66 published vulnerabilities across 4 products and 195 versions from Wolfssl.
None of Wolfssl's vulnerabilities is on the list of flaws known to be exploited today.
Wolfssl, with 58 published vulnerabilities. Its own page lists the ones known to be exploited.
Create a Precursor Intelligence account and track the Wolfssl products you run. We match them against every published flaw, give each one a risk score from 0 to 100 and tell you as soon as we spot one that affects you, by email, in the app or by webhook.