CVE-2017-3731

HIGHNVD 7.58.3▲
EchelonGraph scoreHIGH confidence

Score elevated to 8.3 because EPSS predicts 58% probability of exploitation within the next 30 days (top 1.0% of all CVEs). NVD baseline CVSS 7.5 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, ghsa, nvd
Elevated
8.3EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 58%
CISA-KEV: Not listedEPSS PROB: 58%CVSS: 7.5Exploit: Elevated riskExposed: 0

A fix is available — apply it.

If an SSL/TLS server or client is running on a 32-bit host, and a specific cipher is being used, then a truncated packet can cause that server or client to perform an out-of-bounds read, usually resulting in a crash. For OpenSSL 1.1.0, the crash can be triggered when using CHACHA20/POLY1305; users should upgrade to 1.1.0d. For Openssl 1.0.2, the crash can be triggered when using RC4-MD5; users who have not disabled that algorithm should update to 1.0.2k.

CVSS v3
7.5
EG Score
8.3(high)
EG Risk
65(Track)
EG Risk 65/100SSVC: Track

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
Severity83% × 45%
Exploitation58% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
58%
EPSS %ILE
99%
KEV
Not listed

Published

May 4, 2017

Last Modified

June 17, 2026

References (40)

Patch Availability(5)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulibssl1.0.0 (1.0.2g-1ubuntu9.1) @ yakkety2026-05-22ubuntu
redhatjbcs-httpd24-openssl-1:1.0.2n-11.jbcs.el62018-07-12redhat
redhatjbcs-httpd24-openssl-1:1.0.2n-11.jbcs.el72018-07-12redhat
redhatopenssl2018-07-12redhat
redhatopenssl-1:1.0.1e-60.el7_3.12017-02-20redhat

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

(9 across 9 ecosystems)
Alpine:v3.2(1)
PackageVulnerable rangeFixed inDependents
openssl—1.0.2k-r0—
Alpine:v3.3(1)
PackageVulnerable rangeFixed inDependents
openssl—1.0.2k-r0—
Alpine:v3.4(1)
PackageVulnerable rangeFixed inDependents
openssl—1.0.2k-r0—
Debian:11(1)
PackageVulnerable rangeFixed inDependents
openssl—1.1.0d-1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
openssl—1.1.0d-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
openssl—1.1.0d-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
openssl—1.1.0d-1—
Debian:7(1)
PackageVulnerable rangeFixed inDependents
openssl1.0.1e-2 ... 1.0.1t-1+deb7u1 (45 versions)1.0.1t-1+deb7u2—
Debian:8(1)
PackageVulnerable rangeFixed inDependents
openssl1.0.1k-3 ... 1.0.1t-1+deb8u5 (12 versions)1.0.1t-1+deb8u6—

Weakness Classification(1)

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2017-3731?
CVE-2017-3731 is a high vulnerability published on May 4, 2017. If an SSL/TLS server or client is running on a 32-bit host, and a specific cipher is being used, then a truncated packet can cause that server or client to perform an out-of-bounds read, usually resulting in a crash. For OpenSSL 1.1.0, the crash can be triggered when using CHACHA20/POLY1305; users…
When was CVE-2017-3731 disclosed?
CVE-2017-3731 was first published in the National Vulnerability Database on May 4, 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-3731 actively exploited?
CVE-2017-3731 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 58% probability of exploitation in the next 30 days, which ranks it in the top 1.0% of all scored CVEs.
What is the CVSS score of CVE-2017-3731?
CVE-2017-3731 has a CVSS v3 base score of 7.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 8.3.
How do I remediate CVE-2017-3731?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-3731, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2017-3731

Explore →

Is Your Infrastructure Affected by CVE-2017-3731?

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

Start Free Scan →Browse All CVEs