OpenSSL vulnerabilities1 known to be exploited.

Vendor1 known exploited
The short answer

OpenSSL has 257 published vulnerabilities across 2 products in our catalogue. 1 of them is on the list of flaws known to be exploited, so criminals are using them now. The most affected product is OpenSSL, with 256. If you run OpenSSL software, patch the exploited flaws first.

See the exploited flaws

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.

Products

Which OpenSSL products have the most vulnerabilities?

OpenSSL leads with 256 published vulnerabilities. Open a product to see its versions and which of its flaws criminals are already using.

  1. OpenSSL256
  2. Fips Object Module1
Published vulnerabilities
Known exploited

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.

  1. 7.5
    CVE-2014-0160HighKnown exploited
    OpenSSL 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.

    Chance of use>99%Known exploited since4 May 2022
Exploit likelihood

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.

50% or more10% to 49%Under 10%
  1. >99%
    CVE-2014-0160HighKnown exploited

    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...

    CVSS7.5Published7 Apr 2014
  2. >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...

    CVSS3.4Published15 Oct 2014
  3. >99%

    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...

    CVSS6.8Published5 Jun 2014
  4. >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...

    CVSS3.7Published21 May 2015
  5. 99%

    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...

    CVSS4.3Published9 Jan 2015
  6. 96%

    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...

    CVSS7.3Published21 Jun 2022
  7. 95%

    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...

    CVSS7.4Published5 Jun 2014
  8. 95%

    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...

    CVSS7.5Published1 Sep 2016
  9. 92%

    A buffer overrun can be triggered in X.509 certificate verification, specifically in name constraint checking.

    CVSS7.5Published1 Nov 2022
  10. 91%

    A buffer overrun can be triggered in X.509 certificate verification, specifically in name constraint checking.

    CVSS7.5Published1 Nov 2022
Every product

All OpenSSL products we track.

2 products, most vulnerabilities first. Find the ones you run, then open a product to see its versions and exploited flaws.

EdgeProtect

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.

  1. Tell us what you runPick your software from a list, or let us work it out from your website.
  2. We match it to every flawOver 400,000 published flaws, checked against your list.
  3. Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
  4. 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.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

Our catalogue lists 257 published vulnerabilities across 2 products and 246 versions from OpenSSL. The most recent OpenSSL flaw added to the known-exploited list is CVE-2014-0160, on 4 May 2022.

1 OpenSSL vulnerability is on the list of flaws known to be exploited. The most recently added is CVE-2014-0160. The full list is on this page.

OpenSSL, with 256 published vulnerabilities. Its own page lists the ones known to be exploited.

Create a EdgeProtect account and track the OpenSSL 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.