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
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.
- Exploited
- Not confirmed
- Reports
- 0
- Tactics
- 0/15
Exploitation timelineDated milestones for a CVE: when it was disclosed, when exploit code became public, when exploitation was confirmed, and when threat reports named it.
Disclosed on 7 Dec 2017. No public exploit code or confirmed exploitation is recorded.
Patch historyEarlier and later CVEs in the same code, in date order. It shows when a fix was bypassed or incomplete and which version finally fixed it.
See the family tree8 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.
relatedMedium
Why these are linked: Link confidenceHow strong the evidence is that two CVEs are related. High: stated in the CVE text or linked in an advisory, or the same code was patched one release apart. Medium: the same code, or a version step plus a similar description. Low: similar description only.
- Same code patched: s3_clnt.c (machine-matched)Functions: ssl3_get_key_exchangecommit b15f876commit ce325c6
relatedMedium
Why these are linked: Link confidenceHow strong the evidence is that two CVEs are related. High: stated in the CVE text or linked in an advisory, or the same code was patched one release apart. Medium: the same code, or a version step plus a similar description. Low: similar description only.
- Same code patched: s3_srvr.c (machine-matched)commit ce325c6commit 1421e0c
- same family
relatedMedium
Why these are linked: Link confidenceHow strong the evidence is that two CVEs are related. High: stated in the CVE text or linked in an advisory, or the same code was patched one release apart. Medium: the same code, or a version step plus a similar description. Low: similar description only.
- Same code patched: ssl_locl.h (machine-matched)commit 98ece4ecommit 4ad9361
- same familyThis CVECVE-2017-3737OpenSSL 1.0.2 (starting from version 1.0.2b) introduced an…7 Dec 2017
- same family
relatedMedium
Why these are linked: Link confidenceHow strong the evidence is that two CVEs are related. High: stated in the CVE text or linked in an advisory, or the same code was patched one release apart. Medium: the same code, or a version step plus a similar description. Low: similar description only.
- Same code patched: ssl_lib.c (machine-matched)commit e9d7083commit 7e4d731commit e86ac43commit 99fb785
Affected versions and fixes
as published in the CVE recordOpenSSL Software Foundation OpenSSL
Affected: 1.0.2b-1.0.2m
What security researchers reported
Not named in any threat report yetAlso mentioned in 2 community threat pulses (AlienVault OTX)
Weaker evidencePulses are indicator collections that anyone can publish. A mention is not confirmation of exploitation.
- SMS Phisphing Campaign16 May 2022
- Internal CVE Research9 Mar 2022