CVE-2017-3737 Details
Description
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.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
No SSVC data is available for this CVE.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-125 | Out-of-bounds Read | [email protected] |
| CWE-787 | Out-of-bounds Write | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| openssl openssl | 1.0.2b 1.0.2c 1.0.2d 1.0.2e 1.0.2f 1.0.2g 1.0.2h 1.0.2i 1.0.2j 1.0.2k 1.0.2l 1.0.2m |
CPE
Remediation
| |
| debian debian linux | 9.0 |
CPE
Remediation
| |
Change History
22 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | [email protected] |
| May 13, 2026 | CVE Status Change | [email protected] |
| Nov 21, 2024 | CVE Modified | CVE |
| May 14, 2024 | CVE Modified | [email protected] |
| Oct 3, 2019 | CWE Remap | [email protected] |
| Jul 23, 2019 | CVE Modified | [email protected] |
| Aug 9, 2018 | CVE Modified | [email protected] |
| Jul 19, 2018 | CVE Modified | [email protected] |
| Jul 14, 2018 | CVE Modified | [email protected] |
| Apr 21, 2018 | CVE Modified | [email protected] |
| Apr 20, 2018 | CVE Modified | [email protected] |
| Apr 12, 2018 | CVE Modified | [email protected] |
| Jan 24, 2018 | CVE Modified | [email protected] |
| Jan 18, 2018 | CVE Modified | [email protected] |
| Jan 18, 2018 | CVE Modified | [email protected] |
| Dec 22, 2017 | Initial Analysis | [email protected] |
| Dec 19, 2017 | CVE Modified | [email protected] |
| Dec 16, 2017 | CVE Modified | [email protected] |
| Dec 14, 2017 | CVE Modified | [email protected] |
| Dec 11, 2017 | CVE Modified | [email protected] |
| Dec 10, 2017 | CVE Modified | [email protected] |
| Dec 9, 2017 | CVE Modified | [email protected] |