Patchfirst
CVE-2017-3737 EPSS 78.7%

OpenSSL 1.0.2 (starting from version 1.0.2b) introduced an "error state" mechanism

No fixed version listed yet.Check the vendor advisory. References ↓

OpenSSL Software Foundation · OpenSSL

Summary

OpenSSL 1.0.2 (from 1.0.2b onward) has a bug in its error-state handling, where a handshake failure does not block subsequent SSL_read() or SSL_write() calls made directly on the same SSL object. An attacker can exploit this only where the application itself calls SSL_read() or SSL_write() after receiving a fatal handshake error, so the application code must contain that flaw for the issue to be reachable.

Official description · CVE.org

OpenSSL 1.0.2 (starting from version 1.0.2b) introduced an "error state" mechanism. The intent was that if a fatal error occurred during a handshake then OpenSSL would move into the error state and would immediately fail if you attempted to continue the handshake. This works as designed for the explicit handshake functions (SSL_do_handshake(), SSL_accept() and SSL_connect()), however due to a bug it does not work correctly if SSL_read() or SSL_write() is called directly. In that scenario, if the handshake fails then a fatal error will be returned in the initial function call. If SSL_read()/SSL_write() is subsequently called by the application for the same SSL object then it will succeed and the data is passed without being decrypted/encrypted directly from the SSL/TLS record layer. In order to exploit this issue an application bug would have to be present that resulted in a call to SSL_read()/SSL_write() being issued after having already received a fatal error. OpenSSL version 1.0.2b-1.0.2m are affected. Fixed in OpenSSL 1.0.2n. OpenSSL 1.1.0 is not affected.

Breakdown
21.0 / 100
Exploited
Not confirmed
Reports
0
Tactics
0/15

Disclosed on 7 Dec 2017. No public exploit code or confirmed exploitation is recorded.

See the family tree

8 related vulnerabilities in the same code over 9 years.

Same bug familyLinked by evidence that a fix failed or the same code was patched again. Oldest first.

  1. CVE-2014-3572The ssl3_get_key_exchange function in s3_clnt.c in OpenSSL…9 Jan 2015
  2. relatedMedium

    Why these are linked:

    CVE-2015-0204The ssl3_get_key_exchange function in s3_clnt.c in OpenSSL…9 Jan 2015
  3. relatedMedium

    Why these are linked:

    CVE-2015-0205The ssl3_get_cert_verify function in s3_srvr.c in OpenSSL 1.0.0…9 Jan 2015
  4. same family
    CVE-2015-1791Race condition in the ssl3_get_new_session_ticket function in…12 Jun 2015
  5. relatedMedium

    Why these are linked:

    CVE-2017-3733Encrypt-Then-Mac renegotiation crash4 May 2017
  6. same family
    This CVECVE-2017-3737OpenSSL 1.0.2 (starting from version 1.0.2b) introduced an…7 Dec 2017
  7. same family
    CVE-2024-2511Unbounded memory growth with session handling in TLSv1.38 Apr 2024
  8. relatedMedium

    Why these are linked:

    CVE-2024-5535SSL_select_next_proto buffer overread27 Jun 2024

Affected versions and fixes

as published in the CVE record

OpenSSL Software Foundation OpenSSL

Affected: 1.0.2b-1.0.2m

What security researchers reported

Not named in any threat report yet

Also mentioned in 2 community threat pulses (AlienVault OTX)

Weaker evidence

Pulses are indicator collections that anyone can publish. A mention is not confirmation of exploitation.

References

21 links, grouped by NVD tag
↑ ↓ chooseEnter openEsc close