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.
CVE-2017-3731
HIGHNVD 7.58.2Trending — 3 sources updated this weekElevatedEG-KEV Tier 3: ElevatedEG-KEV is EchelonGraph's own tiering of exploitation signals from CISA KEV, CISA's SSVC data (Vulnrichment), ransomware data, public exploit-code references and EPSS.Tier 3 is not evidence of exploitation. It means public exploit code is referenced, or CISA's SSVC data says "public PoC", or EPSS ranks the CVE in the top 5%.Signals for this CVE: EPSS in the top 5%, EPSS 50% or more.EchelonGraph confidence 38%: a heuristic from the tier and the number of signals, not a measured probability.
EchelonGraph scoreHIGH confidence
“▲” beside the score: it is higher than NVD's CVSS score.
Score elevated to 8.2 because EPSS predicted 57% probability of exploitation within the next 30 days (99th percentile of EPSS-scored CVEs) when EchelonGraph scored this CVE. NVD baseline CVSS 7.5 retained for reference. Confidence: see factors.
Triggered by: EPSS exploit prediction (continuous uplift above 30%)
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
8.2EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
- High exploitation likelihood — EPSS 57%
CISA-KEV: Not listedEPSS PROB: 57%CVSS: 7.5Exploit: No code on recordExposed services: Not assessed
A fix is available — apply it.
- CVSS v3
- 7.5
- EG Score
- 8.2HIGHhigh confidence
- EG Risk
- 60EG Risk 60/100
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 (value × EchelonGraph’s weight)Severity82% × 45%The EG Score, 8.2 of 10.Exploitation57% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability0% × 15%CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- 57%
- EPSS %ILE
- 99th
- KEV
- Not listed
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines.
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
May 4, 2017
Last Modified
June 17, 2026
References (20)
- openssl-security@openssl · CVE Programhttp://rhn.redhat.com/errata/RHSA-2017-0286.htmlThird Party Advisory
- openssl-security@openssl · CVE Programhttp://www.debian.org/security/2017/dsa-3773Third Party Advisory
- openssl-security@openssl · CVE Programhttp://www.oracle.com/technetwork/security-advisory/cpujan2018-3236628.htmlPatch · Third Party Advisory
- openssl-security@openssl · CVE Programhttp://www.oracle.com/technetwork/security-advisory/cpujul2017-3236622.htmlPatch · Third Party Advisory
- openssl-security@openssl · CVE Programhttp://www.oracle.com/technetwork/security-advisory/cpuoct2017-3236626.htmlPatch · Third Party Advisory
- openssl-security@openssl · CVE Programhttp://www.securityfocus.com/bid/95813 (archived copy: the site no longer serves it)Third Party Advisory · VDB Entry
- openssl-security@openssl · CVE Programhttp://www.securitytracker.com/id/1037717Third Party Advisory · VDB Entry
- openssl-security@openssl · CVE Programhttps://access.redhat.com/errata/RHSA-2018:2185Third Party Advisory
- openssl-security@openssl · CVE Programhttps://access.redhat.com/errata/RHSA-2018:2186Third Party Advisory
- openssl-security@openssl · CVE Programhttps://access.redhat.com/errata/RHSA-2018:2187Third Party Advisory
- openssl-security@openssl · CVE Programhttps://github.com/openssl/openssl/commit/00d965474b22b54e4275232bc71ee0c699c5cd21Third Party Advisory
- openssl-security@openssl · CVE Programhttps://security.FreeBSD.org/advisories/FreeBSD-SA-17:02.openssl.ascThird Party Advisory
- openssl-security@openssl · CVE Programhttps://security.gentoo.org/glsa/201702-07Third Party Advisory
- openssl-security@openssl · CVE Programhttps://security.netapp.com/advisory/ntap-20171019-0002/Third Party Advisory
- openssl-security@openssl · CVE Programhttps://security.paloaltonetworks.com/CVE-2017-3731Third Party Advisory
15 of 20 shown · show the other 5
- openssl-security@openssl · CVE Programhttps://source.android.com/security/bulletin/pixel/2017-11-01Third Party Advisory
- openssl-security@openssl · CVE Programhttps://support.hpe.com/hpsc/doc/public/display?docLocale=en_US&docId=emr_na-hpesbhf03838en_usThird Party Advisory
- openssl-security@openssl · CVE Programhttps://www.openssl.org/news/secadv/20170126.txtVendor Advisory
- openssl-security@openssl · CVE Programhttps://www.oracle.com/technetwork/security-advisory/cpuapr2019-5072813.htmlPatch · Third Party Advisory
- openssl-security@openssl · CVE Programhttps://www.tenable.com/security/tns-2017-04Third Party Advisory
Vendor Advisories for CVE-2017-3731(2)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(5)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| ubuntu | libssl1.0.0 (1.0.2g-1ubuntu9.1) @ yakkety | 2026-05-22 | ubuntu |
| redhat | jbcs-httpd24-openssl-1:1.0.2n-11.jbcs.el6 | 2018-07-12 | redhat |
| redhat | jbcs-httpd24-openssl-1:1.0.2n-11.jbcs.el7 | 2018-07-12 | redhat |
| redhat | openssl | 2018-07-12 | redhat |
| redhat | openssl-1:1.0.1e-60.el7_3.1 | 2017-02-20 | redhat |
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)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| openssl | — |
| — |
Alpine:v3.3(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| openssl | — |
| — |
Alpine:v3.4(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| openssl | — |
| — |
Debian:11(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| openssl | — |
| — |
Debian:12(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| openssl | — |
| — |
Debian:13(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| openssl | — |
| — |
Debian:14(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| openssl | — |
| — |
Debian:7(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| openssl | 1.0.1e-2 ... 1.0.1t-1+deb7u1 (45 versions) |
| — |
Debian:8(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| openssl | 1.0.1k-3 ... 1.0.1t-1+deb8u5 (12 versions) |
| — |
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.
- Red HatRHSA-2017:0286MODERATE2017-01-26
RHSA-2017:0286 — Moderate
- Red HatRHSA-2018:2185MODERATE2017-01-26
RHSA-2018:2185 — Moderate
- Red HatRHSA-2018:2186MODERATE2017-01-26
RHSA-2018:2186 — Moderate
- Red HatRHSA-2018:2187MODERATE2017-01-26
RHSA-2018:2187 — Moderate
- UbuntuUSN-3181-1MEDIUM
OpenSSL vulnerabilities
Data Freshness Timeline
(refreshed 7× in last 7d / 19× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
Showing the most recent 85 of 114 refreshes on record for this CVE.
A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 15 repeat rows among the latest 100 are merged into the row they repeat. The 29 oldest rows on record are not shown and were not checked, so the counts can still include repeats.
- 2026-10-12 00:51 UTCEG score recompute
- 2026-10-11 13:41 UTCEPSS rescoreEPSS 57% · 99th percentile
- 2026-10-10 19:55 UTCEPSS rescoreEPSS 57% · 99th percentile
- 2026-10-09 20:02 UTCEPSS rescoreEPSS 57% · 99th percentile
- 2026-10-08 06:24 UTCOSV refresh
- 2026-10-07 23:41 UTCEPSS rescoreEPSS 57% · 99th percentile
- 2026-10-06 15:12 UTCEPSS rescoreEPSS 57% · 99th percentile
- 2026-10-03 14:21 UTCEPSS rescoreEPSS 57% · 99th percentile
- 2026-09-30 14:59 UTCEPSS rescoreEPSS 57% · 99th percentile
- 2026-09-30 09:33 UTCEG score recompute▼ 0.10
- 2026-09-28 13:45 UTCEPSS rescoreEPSS 57% · 99th percentile
- 2026-09-27 13:40 UTCEPSS rescoreEPSS 57% · 99th percentile
- 2026-09-26 15:53 UTCEPSS rescoreEPSS 57% · 99th percentile
- 2026-09-24 13:59 UTCEPSS rescoreEPSS 58% · 99th percentile
- 2026-09-18 19:22 UTCEPSS rescoreEPSS 58% · 99th percentile
- 2026-09-18 12:06 UTCOSV refresh
- 2026-09-17 19:22 UTCEPSS rescoreEPSS 58% · 99th percentile
- 2026-09-15 03:05 UTCEPSS rescoreEPSS 58% · 99th percentile
- 2026-09-12 14:55 UTCEPSS rescoreEPSS 58% · 99th percentile
- 2026-09-11 09:31 UTCEPSS rescoreEPSS 58% · 99th percentile
- 2026-09-07 15:56 UTCEPSS rescoreEPSS 58% · 99th percentile
- 2026-09-06 13:43 UTCEPSS rescoreEPSS 58% · 99th percentile
- 2026-09-05 15:23 UTCEPSS rescoreEPSS 58% · 99th percentile
- 2026-09-04 13:56 UTCEPSS rescoreEPSS 58% · 99th percentile
- 2026-09-02 14:07 UTCEPSS rescoreEPSS 58% · 99th percentile
Show 60 moreShow fewer
- 2026-08-30 19:13 UTCEPSS rescoreEPSS 58% · 99th percentile
- 2026-08-30 12:42 UTCOSV refresh
- 2026-08-26 14:41 UTCEPSS rescoreEPSS 58% · 99th percentile
- 2026-08-25 13:44 UTCEPSS rescoreEPSS 58% · 99th percentile
- 2026-08-21 23:44 UTCEPSS rescoreEPSS 58% · 99th percentile
- 2026-08-20 22:51 UTCEPSS rescoreEPSS 58% · 99th percentile
- 2026-08-19 16:59 UTCEPSS rescoreEPSS 58% · 99th percentile
- 2026-08-18 13:43 UTCEPSS rescoreEPSS 58% · 99th percentile
- 2026-08-17 13:42 UTCEPSS rescoreEPSS 58% · 98th percentile
- 2026-08-16 14:51 UTCEPSS rescoreEPSS 58% · 99th percentile
- 2026-08-16 02:10 UTCEPSS rescoreEPSS 58% · 99th percentile
- 2026-08-15 01:26 UTCEPSS rescoreEPSS 58% · 98th percentile
- 2026-08-14 02:48 UTCOSV refresh
- 2026-08-12 13:46 UTCEPSS rescoreEPSS 58% · 98th percentile
- 2026-08-07 16:22 UTCEPSS rescoreEPSS 58% · 98th percentile
- 2026-08-05 19:12 UTCEPSS rescoreEPSS 58% · 98th percentile
- 2026-08-01 04:11 UTCEPSS rescoreEPSS 58% · 98th percentile
- 2026-07-30 01:26 UTCEPSS rescoreEPSS 58% · 98th percentile
- 2026-07-29 07:33 UTCOSV refresh
- 2026-07-28 15:32 UTCEPSS rescoreEPSS 58% · 98th percentile
- 2026-07-26 14:51 UTCEPSS rescoreEPSS 58% · 98th percentile
- 2026-07-23 14:15 UTCEPSS rescoreEPSS 58% · 98th percentile
- 2026-07-23 01:29 UTCEG score recompute▲ 0.80
- 2026-07-22 22:09 UTCEG score recompute
- 2026-07-22 14:04 UTCEPSS rescoreEPSS 58% · 98th percentile
- 2026-07-21 15:21 UTCEPSS rescoreEPSS 58% · 98th percentile
- 2026-07-20 17:04 UTCEPSS rescoreEPSS 58% · 98th percentile
- 2026-07-19 14:28 UTCEPSS rescoreEPSS 58% · 98th percentile
- 2026-07-19 02:26 UTCEPSS rescoreEPSS 58% · 98th percentile
- 2026-07-18 10:00 UTCEPSS rescoreEPSS 58% · 98th percentile
- 2026-07-16 16:59 UTCEPSS rescoreEPSS 58% · 98th percentile
- 2026-07-15 16:54 UTCEPSS rescoreEPSS 58% · 98th percentile
- 2026-07-13 22:26 UTCEPSS rescoreEPSS 58% · 98th percentile
- 2026-07-12 05:43 UTCEPSS rescoreEPSS 58% · 98th percentile
- 2026-07-11 23:52 UTCOSV refresh
- 2026-07-11 08:24 UTCEPSS rescoreEPSS 58% · 98th percentile
- 2026-07-08 15:10 UTCEPSS rescoreEPSS 58% · 98th percentile
- 2026-07-05 02:27 UTCEPSS rescoreEPSS 58% · 98th percentile
- 2026-07-02 16:54 UTCEPSS rescoreEPSS 58% · 98th percentile
- 2026-07-01 15:02 UTCEPSS rescoreEPSS 58% · 98th percentile
- 2026-06-30 23:19 UTCEPSS rescoreEPSS 58% · 98th percentile
- 2026-06-28 04:53 UTCEPSS rescoreEPSS 58% · 98th percentile
- 2026-06-27 03:05 UTCEPSS rescoreEPSS 58% · 98th percentile
- 2026-06-25 13:47 UTCEPSS rescoreEPSS 58% · 98th percentile
- 2026-06-23 21:30 UTCEPSS rescoreEPSS 58% · 98th percentile
- 2026-06-23 06:00 UTCOSV refresh
- 2026-06-22 14:23 UTCEPSS rescoreEPSS 58% · 98th percentile
- 2026-06-21 01:57 UTCEPSS rescoreEPSS 58% · 98th percentile
- 2026-06-19 19:23 UTCEPSS rescoreEPSS 58% · 98th percentile
- 2026-06-18 17:50 UTCEPSS rescoreEPSS 58% · 98th percentile
- 2026-06-17 17:50 UTCEPSS rescoreEPSS 58% · 98th percentile
- 2026-06-16 17:50 UTCEPSS rescoreEPSS 58% · 98th percentile
- 2026-06-15 17:45 UTCEPSS rescoreEPSS 58% · 98th percentile
- 2026-06-14 23:14 UTCEPSS rescoreEPSS 10% · 93rd percentile
- 2026-06-13 22:57 UTCEPSS rescoreEPSS 10% · 93rd percentile
- 2026-06-12 23:09 UTCEPSS rescoreEPSS 10% · 93rd percentile
- 2026-06-10 22:15 UTCEPSS rescoreEPSS 10% · 93rd percentile
- 2026-06-10 13:19 UTCEPSS rescoreEPSS 10% · 93rd percentile
- 2026-06-07 15:22 UTCEPSS rescoreEPSS 10% · 93rd percentile
- 2026-06-06 13:45 UTCEPSS rescoreEPSS 10% · 93rd percentile
Related CVEs(same product + same vendor + same CWE)
Same product
10 shownAlpine:v3.2:openssl
- CVE-2016-6303EG 9.8EPSS p98CRITICAL
- CVE-2016-2182EG 9.8EPSS p99CRITICAL
- CVE-2016-2177EG 9.8EPSS p99CRITICAL
- CVE-2016-2107NVD 5.9EG 9.0EPSS p100CRITICAL
- CVE-2016-6304NVD 7.5EG 8.4EPSS p99HIGH
- CVE-2016-2105NVD 7.5EG 7.8EPSS p99HIGH
- CVE-2016-6302EG 7.5EPSS p98HIGH
- CVE-2016-2181EG 7.5EPSS p98HIGH
- CVE-2016-2179EG 7.5EPSS p98HIGH
- CVE-2016-2180EG 7.5EPSS p98HIGH
Same vendor
10 shownredhat:RHSA-2018:2185 · redhat:RHSA-2017:0286
- CVE-2016-7055EG 5.9EPSS p97MEDIUM
- CVE-2017-3732EG 5.9EPSS p97MEDIUM
- CVE-2016-2182EG 9.8EPSS p99CRITICAL
- CVE-2017-3737NVD 5.9EG 8.6EPSS p100HIGH
- CVE-2016-6302EG 7.5EPSS p98HIGH
- CVE-2016-6306NVD 5.9EG 6.6EPSS p99MEDIUM
- CVE-2017-3736EG 6.5EPSS p96MEDIUM
- CVE-2017-3738EG 5.9EPSS p96MEDIUM
- CVE-2016-8610NVD 7.5EG 7.8EPSS p99HIGH
- CVE-2016-4975EG 6.1EPSS p97MEDIUM
Same CWE
10 shownCWE-125
Frequently asked(5)
What is CVE-2017-3731?
CVE-2017-3731 is a high-severity vulnerability; its CVE record was 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 made public?
CVE-2017-3731 was made public on January 26, 2017: that is the date its CVE record's CNA, OpenSSL Software Foundation, gives for when the vulnerability was made public. The CVE record itself was published on May 4, 2017. EchelonGraph's copy of the record carries a last-modified date of June 17, 2026; the record at its source may have been updated since.
Is CVE-2017-3731 actively exploited?
CVE-2017-3731 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 57% probability of exploitation in the next 30 days (99th percentile of EPSS-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.2 (HIGH).
How do I remediate CVE-2017-3731?
A fix for CVE-2017-3731 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2017-3731 are linked in the Vendor Advisories panel on this page.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2017-3731
Is Your Infrastructure Affected by CVE-2017-3731?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.