OpenSSL vulnerabilitiesAnd the versions its exploited flaws hit.
OpenSSL is made by OpenSSL. We track 256 published vulnerabilities in it, across 245 versions. 1 of them is on the list of flaws known to be exploited, the newest added on 4 May 2022. If you run OpenSSL, check your version against the exploited flaws below and patch those first.
The most recent OpenSSL flaw added to the known-exploited list is CVE-2014-0160, on 4 May 2022. We keep watching the known-exploited list.
Which versions of OpenSSL do the exploited flaws hit?
Each exploited flaw lists the versions it affects, usually as ranges. "1.0.1 to before 1.0.1g" means from 1.0.1 up to, but not including, 1.0.1g. Find your version, then patch.
- CVE-2014-0160Exploited list, 4 May 2022
OpenSSL Information Disclosure Vulnerability
1.0.1 to before 1.0.1g
Which OpenSSL vulnerabilities are being exploited?
1 flaw is on the government list of vulnerabilities known to be exploited. These are the ones criminals are using now, so they go first, whatever their severity score says.
- 7.5OpenSSL Information Disclosure Vulnerability
The TLS and DTLS implementations in OpenSSL do not properly handle Heartbeat Extension packets, which allows remote attackers to obtain sensitive information.
Which OpenSSL 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.
- >99%
The (1) TLS and (2) DTLS implementations in OpenSSL 1.0.1 before 1.0.1g do not properly handle Heartbeat Extension packets, which allows remote attackers to obtain sensitive information from process memory via...
- >99%
The SSL protocol 3.0, as used in OpenSSL through 1.0.1i and other products, uses nondeterministic CBC padding, which makes it easier for man-in-the-middle attackers to obtain cleartext data via a padding-oracle...
- >99%CVE-2014-0195Medium
The dtls1_reassemble_fragment function in d1_both.c in OpenSSL before 0.9.8za, 1.0.0 before 1.0.0m, and 1.0.1 before 1.0.1h does not properly validate fragment lengths in DTLS ClientHello messages, which allows...
- >99%
The TLS protocol 1.2 and earlier, when a DHE_EXPORT ciphersuite is enabled on a server but not on a client, does not properly convey a DHE_EXPORT choice, which allows man-in-the-middle attackers to conduct...
- 99%CVE-2015-0204Medium
The ssl3_get_key_exchange function in s3_clnt.c in OpenSSL before 0.9.8zd, 1.0.0 before 1.0.0p, and 1.0.1 before 1.0.1k allows remote SSL servers to conduct RSA-to-EXPORT_RSA downgrade attacks and facilitate...
- 96%CVE-2022-2068High
In addition to the c_rehash shell command injection identified in CVE-2022-1292, further circumstances where the c_rehash script does not properly sanitise shell metacharacters to prevent command injection were found...
- 95%CVE-2014-0224High
OpenSSL before 0.9.8za, 1.0.0 before 1.0.0m, and 1.0.1 before 1.0.1h does not properly restrict processing of ChangeCipherSpec messages, which allows man-in-the-middle attackers to trigger use of a zero-length master...
- 95%CVE-2016-2183High
The DES and Triple DES ciphers, as used in the TLS, SSH, and IPSec protocols and other protocols and products, have a birthday bound of approximately four billion blocks, which makes it easier for remote attackers to...
- 92%CVE-2022-3786High
A buffer overrun can be triggered in X.509 certificate verification, specifically in name constraint checking.
- 91%CVE-2022-3602High
A buffer overrun can be triggered in X.509 certificate verification, specifically in name constraint checking.
Running OpenSSL? 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 flaw being exploited affects software Acme tracks
The TLS and DTLS implementations in OpenSSL do not properly handle Heartbeat Extension packets, which allows remote attackers to obtain sensitive information.
- Matched to
- OpenSSL on Acme's software list
- What to do
- Patch first, then check for signs of use
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 256 published vulnerabilities listed under the name OpenSSL, across 245 versions. The most recent OpenSSL flaw added to the known-exploited list is CVE-2014-0160, on 4 May 2022.
1 is on the list of flaws known to be exploited. The most recently added is CVE-2014-0160.
Each flaw names its own versions, usually as ranges. The newest, CVE-2014-0160, affects 1.0.1 to before 1.0.1g. The versions for every exploited flaw are listed on this page.
Create a Precursor Intelligence account and track OpenSSL. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.