CVE-2017-3737

MEDIUMNVD 5.95.9—
EchelonGraph scoreMEDIUM confidence

Score 5.9 from GitHub Security Advisory published 2022-05-13. NVD baseline CVSS 5.9; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Elevated
5.9
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 79%
CISA-KEV: Not listedEPSS: 79%CVSS: 5.9Exploit: NoneExposed: 0

A fix is available — apply it.

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.

CVSS v3
5.9
EG Score
5.9(medium)
EPSS
99.5%
KEV
Not listed

Published

December 7, 2017

Last Modified

May 13, 2026

References (42)

Patch Availability(5)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulibssl1.0.0 (1.0.2g-1ubuntu11.4) @ zesty2026-05-22ubuntu
redhatjbcs-httpd24-openssl-1:1.0.2n-11.jbcs.el72018-07-12redhat
redhatopenssl2018-07-12redhat
redhatjbcs-httpd24-openssl-1:1.0.2n-11.jbcs.el62018-07-12redhat
redhatopenssl-1:1.0.2k-12.el72018-04-10redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

All Vendor Advisories

(5)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 3× in last 7d / 21× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-07 13:42 UTCEPSS rescore
  2. 2026-07-02 16:54 UTCEPSS rescore
  3. 2026-07-01 15:02 UTCEPSS rescore
  4. 2026-06-25 13:47 UTCEPSS rescore
  5. 2026-06-24 14:02 UTCEPSS rescore
  6. 2026-06-24 14:02 UTCEPSS rescore
  7. 2026-06-23 21:30 UTCEPSS rescore
  8. 2026-06-22 20:35 UTCOSV refresh
  9. 2026-06-21 14:54 UTCEPSS rescore
  10. 2026-06-21 14:54 UTCEPSS rescore
  11. 2026-06-17 17:50 UTCEPSS rescore
  12. 2026-06-16 17:50 UTCEPSS rescore
  13. 2026-06-16 17:50 UTCEPSS rescore
  14. 2026-06-15 17:45 UTCEPSS rescore
  15. 2026-06-14 23:14 UTCEPSS rescore
  16. 2026-06-13 22:57 UTCEPSS rescore
  17. 2026-06-12 23:09 UTCEPSS rescore
  18. 2026-06-10 22:15 UTCEPSS rescore
  19. 2026-06-10 13:19 UTCEPSS rescore
  20. 2026-06-08 14:14 UTCEPSS rescore
  21. 2026-06-08 14:14 UTCEPSS rescore
  22. 2026-06-07 15:22 UTCEPSS rescore
  23. 2026-06-07 15:22 UTCEPSS rescore
  24. 2026-06-06 13:45 UTCEPSS rescore
  25. 2026-06-06 13:45 UTCEPSS rescore
Show 33 more
  1. 2026-06-05 22:44 UTCEPSS rescore
  2. 2026-06-05 11:27 UTCOSV refresh
  3. 2026-06-05 06:08 UTCEPSS rescore
  4. 2026-06-05 06:08 UTCEPSS rescore
  5. 2026-06-04 13:10 UTCEPSS rescore
  6. 2026-06-02 20:11 UTCEPSS rescore
  7. 2026-06-02 20:11 UTCEPSS rescore
  8. 2026-05-31 22:28 UTCEPSS rescore
  9. 2026-05-31 22:28 UTCEPSS rescore
  10. 2026-05-31 00:14 UTCEPSS rescore
  11. 2026-05-31 00:14 UTCEPSS rescore
  12. 2026-05-29 13:41 UTCEPSS rescore
  13. 2026-05-28 13:42 UTCEPSS rescore
  14. 2026-05-28 13:42 UTCEPSS rescore
  15. 2026-05-26 13:42 UTCEPSS rescore
  16. 2026-05-26 13:42 UTCEPSS rescore
  17. 2026-05-26 07:17 UTCEPSS rescore
  18. 2026-05-26 07:17 UTCEPSS rescore
  19. 2026-05-22 21:15 UTCEPSS rescore
  20. 2026-05-22 21:15 UTCEPSS rescore
  21. 2026-05-22 21:15 UTCEPSS rescore
  22. 2026-05-22 21:15 UTCEPSS rescore
  23. 2026-05-22 21:15 UTCEPSS rescore
  24. 2026-05-22 07:26 UTCEG score recompute
  25. 2026-05-22 07:26 UTCVendor advisory
  26. 2026-05-22 07:26 UTCGHSA enrichment
  27. 2026-05-21 22:40 UTCEPSS rescore
  28. 2026-05-20 22:37 UTCEPSS rescore
  29. 2026-05-20 22:37 UTCEPSS rescore
  30. 2026-05-20 22:37 UTCEPSS rescore
  31. 2026-05-20 11:21 UTCEPSS rescore
  32. 2026-05-20 11:21 UTCEPSS rescore
  33. 2026-05-18 21:30 UTCEPSS rescore

Frequently asked(5)

What is CVE-2017-3737?
CVE-2017-3737 is a medium vulnerability published on 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…
When was CVE-2017-3737 disclosed?
CVE-2017-3737 was first published in the National Vulnerability Database on December 7, 2017, with the most recent update on May 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2017-3737 actively exploited?
CVE-2017-3737 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2017-3737?
CVE-2017-3737 has a CVSS v3 base score of 5.9 (NVD).
How do I remediate CVE-2017-3737?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-3737, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2017-3737

Explore →

Is Your Infrastructure Affected by CVE-2017-3737?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs