CVE-2017-3737
Reported by openssl · Published December 7, 2017
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.
Affected products
| Vendor | Product | Versions |
|---|---|---|
| OpenSSL Software Foundation | OpenSSL | 1.0.2b-1.0.2m |
| OpenSSL Software Foundation | OpenSSL | 1.0.2b-1.0.2m |
| amazon:2 | openssl-perl | 0 |
| OpenSSL Software Foundation | OpenSSL | |
| arch | lib32-openssl | 1.1.0.g-1 |
| amazon:2 | openssl-devel | 0 |
| amazon:2 | openssl-libs | 0 |
| alpine | openssl | 0 |
| amazon:2 | openssl-static | 0 |
| arch | openssl | 1.1.0.g-1 |
| amazon:2 | openssl | 0 |
Timeline
- Dec 7, 2017 CVE Published
- Apr 14, 2021 EPSS Score (30 in total, the first dated here)
- Sep 8, 2025 CVE Updated
- Mar 6, 2026 Distribution Patch (8 in total, the first dated here)
- Mar 6, 2026 Security Advisory (9 in total, the first dated here)
- Sep 29, 2026 Coalition ESS Score
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2017-3737
vulnetix vdb fixes CVE-2017-3737
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2017-3737/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart
References
- RHSA-2018:2185 vendor-advisoryx_refsource_REDHAT
- RHSA-2018:2186 vendor-advisoryx_refsource_REDHAT
- x_refsource_CONFIRM
- x_refsource_CONFIRM
- x_refsource_CONFIRM
- x_refsource_CONFIRM
- FreeBSD-SA-17:12 vendor-advisoryx_refsource_FREEBSD
- GLSA-201712-03 vendor-advisoryx_refsource_GENTOO
- 1039978 vdb-entryx_refsource_SECTRACK
- x_refsource_CONFIRM
- x_refsource_MISC
- RHSA-2018:0998 vendor-advisoryx_refsource_REDHAT
- x_refsource_CONFIRM
- DSA-4065 vendor-advisoryx_refsource_DEBIAN
- x_refsource_CONFIRM
- 102103 vdb-entryx_refsource_BID
- x_refsource_CONFIRM
- RHSA-2018:2187 vendor-advisoryx_refsource_REDHAT
- x_refsource_CONFIRM
- x_refsource_CONFIRM
…and 1 more