CVE-2017-3737

HIGHNVD 5.98.6▲
EchelonGraph scoreHIGH confidence

Score elevated to 8.6 because EPSS predicts 79% probability of exploitation within the next 30 days (99th percentile of EPSS-scored CVEs). NVD baseline CVSS 5.9 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction (continuous uplift above 30%)
Sources: epss, ghsa, nvd
Elevated
8.6EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 79%
CISA-KEV: Not listedEPSS PROB: 79%CVSS: 5.9Exploit: Elevated riskExposed services: Not assessed

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
8.6HIGHhigh confidence
EG Risk
75
EG Risk 75/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity86% × 45%
Exploitation79% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track* or Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
79%
EPSS %ILE
99th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* or Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (EG-KEV: elevated) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

December 7, 2017

Last Modified

June 17, 2026

References (42)

Patch Availability(5)

Vendor / EcosystemFix (by version range) / 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.

Affected Packages

(11 across 11 ecosystems)
Alpine:v3.3(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • every version up to 1.0.2n-r0: fixed in 1.0.2n-r0
—
Alpine:v3.4(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • every version up to 1.0.2n-r0: fixed in 1.0.2n-r0
—
Alpine:v3.5(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • every version up to 1.0.2n-r0: fixed in 1.0.2n-r0
—
Alpine:v3.6(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • every version up to 1.0.2n-r0: fixed in 1.0.2n-r0
—
Alpine:v3.7(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • every version up to 1.0.2n-r0: fixed in 1.0.2n-r0
—
Alpine:v3.8(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • every version up to 1.0.2n-r0: fixed in 1.0.2n-r0
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • every version up to 1.1.0b-2: fixed in 1.1.0b-2
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • every version up to 1.1.0b-2: fixed in 1.1.0b-2
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • every version up to 1.1.0b-2: fixed in 1.1.0b-2
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • every version up to 1.1.0b-2: fixed in 1.1.0b-2
—
Debian:9(1)
PackageVulnerable rangeFix by version rangeDependents
openssl1.01.0.2l-2, 1.0.2l-2+deb9u1
  • every version up to 1.0.2l-2+deb9u2: fixed in 1.0.2l-2+deb9u2
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

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 4× in last 7d / 14× 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.

Showing the most recent 100 of 108 total refreshes for this CVE.

  1. 2026-10-10 19:55 UTCEPSS rescore
  2. 2026-10-07 23:41 UTCEPSS rescore
  3. 2026-10-07 20:24 UTCOSV refresh
  4. 2026-10-06 15:12 UTCEPSS rescore
  5. 2026-10-03 14:21 UTCEPSS rescore
  6. 2026-09-30 14:59 UTCEPSS rescore
  7. 2026-09-30 09:33 UTCEG score recompute
  8. 2026-09-24 13:59 UTCEPSS rescore
  9. 2026-09-18 19:22 UTCEPSS rescore
  10. 2026-09-18 02:20 UTCOSV refresh
  11. 2026-09-17 19:22 UTCEPSS rescore
  12. 2026-09-15 03:05 UTCEPSS rescore
  13. 2026-09-15 03:05 UTCEPSS rescore
  14. 2026-09-13 16:42 UTCEPSS rescore
  15. 2026-09-07 15:56 UTCEPSS rescore
  16. 2026-09-06 13:43 UTCEPSS rescore
  17. 2026-09-05 15:23 UTCEPSS rescore
  18. 2026-09-04 13:56 UTCEPSS rescore
  19. 2026-09-02 14:07 UTCEPSS rescore
  20. 2026-09-02 14:07 UTCEPSS rescore
  21. 2026-08-30 19:13 UTCEPSS rescore
  22. 2026-08-30 03:18 UTCOSV refresh
  23. 2026-08-27 14:21 UTCEPSS rescore
  24. 2026-08-25 13:44 UTCEPSS rescore
  25. 2026-08-21 23:44 UTCEPSS rescore
Show 75 more
  1. 2026-08-20 22:51 UTCEPSS rescore
  2. 2026-08-19 16:59 UTCEPSS rescore
  3. 2026-08-18 13:43 UTCEPSS rescore
  4. 2026-08-16 02:10 UTCEPSS rescore
  5. 2026-08-15 01:26 UTCEPSS rescore
  6. 2026-08-13 15:21 UTCOSV refresh
  7. 2026-08-12 13:46 UTCEPSS rescore
  8. 2026-08-07 16:22 UTCEPSS rescore
  9. 2026-08-06 13:42 UTCEPSS rescore
  10. 2026-08-05 19:12 UTCEPSS rescore
  11. 2026-08-02 02:23 UTCEPSS rescore
  12. 2026-08-01 04:11 UTCEPSS rescore
  13. 2026-07-30 01:26 UTCEPSS rescore
  14. 2026-07-28 21:21 UTCOSV refresh
  15. 2026-07-26 14:51 UTCEPSS rescore
  16. 2026-07-23 01:29 UTCEG score recompute▲ 2.70
  17. 2026-07-22 22:09 UTCEG score recompute
  18. 2026-07-22 14:04 UTCEPSS rescore
  19. 2026-07-22 14:04 UTCEPSS rescore
  20. 2026-07-21 15:21 UTCEPSS rescore
  21. 2026-07-21 15:21 UTCEPSS rescore
  22. 2026-07-18 10:00 UTCEPSS rescore
  23. 2026-07-15 16:54 UTCEPSS rescore
  24. 2026-07-11 14:11 UTCOSV refresh
  25. 2026-07-09 19:06 UTCEPSS rescore
  26. 2026-07-07 13:42 UTCEPSS rescore
  27. 2026-07-02 16:54 UTCEPSS rescore
  28. 2026-07-01 15:02 UTCEPSS rescore
  29. 2026-06-25 13:47 UTCEPSS rescore
  30. 2026-06-24 14:02 UTCEPSS rescore
  31. 2026-06-24 14:02 UTCEPSS rescore
  32. 2026-06-23 21:30 UTCEPSS rescore
  33. 2026-06-22 20:35 UTCOSV refresh
  34. 2026-06-21 14:54 UTCEPSS rescore
  35. 2026-06-21 14:54 UTCEPSS rescore
  36. 2026-06-17 17:50 UTCEPSS rescore
  37. 2026-06-16 17:50 UTCEPSS rescore
  38. 2026-06-16 17:50 UTCEPSS rescore
  39. 2026-06-15 17:45 UTCEPSS rescore
  40. 2026-06-14 23:14 UTCEPSS rescore
  41. 2026-06-13 22:57 UTCEPSS rescore
  42. 2026-06-12 23:09 UTCEPSS rescore
  43. 2026-06-10 22:15 UTCEPSS rescore
  44. 2026-06-10 13:19 UTCEPSS rescore
  45. 2026-06-08 14:14 UTCEPSS rescore
  46. 2026-06-08 14:14 UTCEPSS rescore
  47. 2026-06-07 15:22 UTCEPSS rescore
  48. 2026-06-07 15:22 UTCEPSS rescore
  49. 2026-06-06 13:45 UTCEPSS rescore
  50. 2026-06-06 13:45 UTCEPSS rescore
  51. 2026-06-05 22:44 UTCEPSS rescore
  52. 2026-06-05 11:27 UTCOSV refresh
  53. 2026-06-05 06:08 UTCEPSS rescore
  54. 2026-06-05 06:08 UTCEPSS rescore
  55. 2026-06-04 13:10 UTCEPSS rescore
  56. 2026-06-02 20:11 UTCEPSS rescore
  57. 2026-06-02 20:11 UTCEPSS rescore
  58. 2026-05-31 22:28 UTCEPSS rescore
  59. 2026-05-31 22:28 UTCEPSS rescore
  60. 2026-05-31 00:14 UTCEPSS rescore
  61. 2026-05-31 00:14 UTCEPSS rescore
  62. 2026-05-29 13:41 UTCEPSS rescore
  63. 2026-05-28 13:42 UTCEPSS rescore
  64. 2026-05-28 13:42 UTCEPSS rescore
  65. 2026-05-26 13:42 UTCEPSS rescore
  66. 2026-05-26 13:42 UTCEPSS rescore
  67. 2026-05-26 07:17 UTCEPSS rescore
  68. 2026-05-26 07:17 UTCEPSS rescore
  69. 2026-05-22 21:15 UTCEPSS rescore
  70. 2026-05-22 21:15 UTCEPSS rescore
  71. 2026-05-22 21:15 UTCEPSS rescore
  72. 2026-05-22 21:15 UTCEPSS rescore
  73. 2026-05-22 21:15 UTCEPSS rescore
  74. 2026-05-22 07:26 UTCEG score recompute
  75. 2026-05-22 07:26 UTCVendor advisory

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2017-3737?
CVE-2017-3737 is a high 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 on December 7, 2017, with the most recent update on June 17, 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 79% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2017-3737?
CVE-2017-3737 has a CVSS v3 base score of 5.9 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 8.6 (HIGH).
How do I remediate CVE-2017-3737?
A fix for CVE-2017-3737 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by 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.

Book a Demo →Browse All CVEs