vciy

CVE-2017-3731

INDEX BUILT · 2026-09-20

No source can show you its own past. This one can.

Print this page to keep the view as it stands on this date. Everything hidden behind a disclosure opens, and every receipt prints with its value.

Truncated packet could crash via OOB read

CVE-2017-37314 of 4 sources documented this
44

rank 44 = 14 + 19 + 1 + 10 + 0

rank@v1 · scheduled

Someone is already using it

CISA KEV catalog · public proof-of-concept · FIRST EPSS

EPSS 0.57595  ·  without this subject the record ranks 30

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 7.5, from NVD  ·  without this subject the record ranks 25

It is getting worse, not staying still

FIRST EPSS series, rescorings and bad loads removed

rose on 2025-12-01  ·  without this subject the record ranks 43

How much of the world it touches

NVD CPE configurations

19 products in the CPE ranges  ·  without this subject the record ranks 34

Someone else already set the date

CISA KEV remediation due date

no CISA due date  ·  without this subject the record ranks 44

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$1.76Mover the next 30 days, if this record is yours
Movement+$30,100on 2026-05-27, the last material move, 19 days before this reading
Basisassumeda published average, not your estate

$1.76M = $4.99M incident cost x 0.6121449559255632 exposure x 0.57595 likelihood

udv@v1 · unaudited · wrong for you until you say what you run

$4.99M is the cost of a breach that happened, from IBM Cost of a Data Breach Report 2026, global average. It is not the value of any asset of yours. That average already covers breaches of every severity, so scaling it by exposure understates a partial-impact record. That is an assumption, not a measurement. Your own asset value goes in the decision record.

Hindsight · the state

0.57595EPSSNOT IN KEVas of 2026-09-20
Severity7.5 HIGHreceipt
Harmunauthenticated · networkreceipt
Exploitationnone in held sources
Defenseunaffected versions publishedreceipt
Movementthreshold crossedreceipt
RISING10Risen from 0.0427 to 0.57595 across 28 observations. arc-rules@v1

Foresight · where to check next

CVE-2016-4523CVE-2014-0160CVE-2020-11899CVE-2016-1646Google Chrome3731

This record is one instance of CWE-125, out-of-bounds read. The index holds 9767 prior instances of this class, 19 KEV-listed. The nearest of its KEV-listed records are drawn beside this. taxonomy@v1

Full pattern panel

Prior records in this weakness class. Each is its own record, dated and receipted.
Color is a claim, not decoration:the hostile worldthe defenseno signalspoke length is how much of the record matches, not how bad it is

Running OpenSSL? Check your version

A deterministic range check against the ranges this record publishes. It tells you where a version sits in the record, not whether your deployment is exploitable. No account needed.

Watch this record

Matches your own product list against every record this index holds, and tells you when one of them moves.

What counts as a move

Set up a watchlist (needs a Practitioner account)

Record your call

Keep your verdict, your reason and the evidence together. The record takes its date when you save it.

AcceptDeferPatch by…Not affectedMitigated

Choose your verdict, then sign in or use an email link. Your first 100 records are free. Evidence is frozen when the record is created.

Private to your organization unless you share it. Put the proof link in your ticket so a reviewer can inspect the basis for your call. See how decision records work.

Harm, if it fires from the vector and the weakness

Written for the ticket you're about to file.

Reachnetwork-reachable · no privileges required · no user interaction · low attack complexityreceipt
ImpactComplete availability lossreceipt
Scored fromCVSS v3.1 · NVD's vectorreceipt
Weakness classCWE-125 Out-of-bounds Readreceipt
Published consequencesCWE-125: Confidentiality: Read Memory; Confidentiality: Bypass Protection Mechanism; Availability: DoS: Crash, Exit, or Restart; Other: Varies by Context[email protected]

CISA KEV & Federal Remediation Deadline from the record and CISA

The fix, and how long it's been waiting.

First unaffected version, by branchnode.js 4.7.3; node.js 6.9.5; node.js 7.5.0receipt
Patch available sinceNo dated patch-availability record in held sources. The index holds reference URLs without dates and only the current revision of the CVE record, so the day a fix first existed cannot be derived. Only the versions it landed in.

Exploit Status & Known PoCs a ladder, not a score

Current rung: Nothing observed in held sources.

  • RUNG 1Nothing observed in held sources
  • RUNG 2Proof-of-concept published
  • RUNG 3Exploited in the wild · CISA KEV listed
  • RUNG 4Ransomware campaign use known

Authority who says so

CVSS, NVD7.5 HIGHreceipt
Exploit probability0.57595 · top 0.96% of all CVEsreceipt
Blast breadth2 products across 2 vendorsderived
Assigned byopensslreceipt
Recorded changes28 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Affected productOpenSSLreceipt
Published rangesopenssl 1.1.0a; openssl 1.1.0b; openssl 1.1.0c; openssl 1.0.2receipt
Show all 19 published ranges
openssl 1.1.0a
openssl 1.1.0b
openssl 1.1.0c
openssl 1.0.2
openssl 1.0.2a
openssl 1.0.2b
openssl 1.0.2c
openssl 1.0.2d
openssl 1.0.2e
openssl 1.0.2f
openssl 1.0.2h
openssl 1.0.2i
openssl 1.0.2j
nodejs node.js >= 4.0.0 <= 4.1.2
nodejs node.js >= 4.2.0 < 4.7.3
nodejs node.js >= 5.0.0 <= 5.12.0
nodejs node.js >= 6.0.0 <= 6.8.1
nodejs node.js >= 6.9.0 < 6.9.5
nodejs node.js >= 7.0.0 < 7.5.0

A rung lights from a row in the index, never from an assessment. "Held sources" is the true scope of the claim: this index reads the CVE record, NVD, CISA KEV, FIRST's EPSS and public proof-of-concept repositories, and it does not observe attacks.

Did this affect your environment?Answering needs an account.

What it is stated by the CNA

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

NVD's analysis a second authority

severity
7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
weakness
CWE-125
affected versions
openssl 1.1.0a; openssl 1.1.0b; openssl 1.1.0c; and 16 more, listed in full below

check it yourself access.redhat.com access.redhat.com security.netapp.com oracle.com securityfocus.com rhn.redhat.com +14 morereceipt

Dated events

2025-03-17EPSS moved 0.06 to 0.152026-06-15EPSS moved 0.10 to 0.58

Movement the material steps

14 Apr 20210.0427
7 Mar 20230.04228 · scoring model v2023.03.01
17 Mar 20250.14905 · crossed 0.10 · scoring model v2025.03.14
30 Jul 20250.07549 · crossed 0.10
1 Oct 20250.11263 · crossed 0.10
27 Oct 20250.0762 · crossed 0.10
28 Oct 20250.11263 · crossed 0.10
24 May 20260.09416 · crossed 0.10
27 May 20260.10401 · crossed 0.10
15 Jun 20260.57595 · crossed 0.50 · scoring model v2026.06.15
Show all 28 observations
14 Apr 20210.0427
4 Feb 20220.0472
7 Mar 20230.04228
8 May 20230.04740
30 Jun 20230.05292
8 Aug 20230.04552
17 Dec 20240.05568
17 Mar 20250.14905
29 Mar 20250.17642
30 Mar 20250.14905
2 Jul 20250.14829
10 Jul 20250.11164
30 Jul 20250.07549
17 Aug 20250.06872
25 Aug 20250.0762
1 Oct 20250.11263
27 Oct 20250.0762
28 Oct 20250.11263
1 Dec 20250.14955
27 Dec 20250.10291
28 Dec 20250.14955
16 Jan 20260.11263
18 Jan 20260.10653
23 Jan 20260.10401
22 Mar 20260.12609
24 May 20260.09416
27 May 20260.10401
15 Jun 20260.57595

28 observations held. A highlighted step crossed a promotion threshold. A step marked with a scoring model moved because the instrument was replaced, not because the vulnerability changed. receipt

The full biography

EPSS 0.57595Published2017-05-04Index as of2026-06-15

The record had been public for 9 years, 1 month when this index was last written.

Published 2017-05-04 receipt · Index as of 2026-06-15 derived

The pattern, elsewhere

This record is one instance of CWE-125, out-of-bounds read. The index holds 9767 prior instances of this class, 19 KEV-listed. The nearest of its KEV-listed records are drawn beside this. [email protected]

CVE-2016-4523matches 8 of 8KEV listed · 2016receipt
CVE-2014-0160matches 6 of 8KEV listed · 2014receipt
CVE-2020-11899matches 5 of 8KEV listed · 2020receipt
CVE-2016-1646matches 5 of 8KEV listed · 2016receipt
CVE-2026-11645 · Google Chromematches 5 of 9KEV listed · 2026receipt
CVE-2024-0519 · Google Chromematches 5 of 9KEV listed · 2024receipt

"Matches n of m" counts the attributes the two records can both be compared on: the CVSS metrics they share a version of, any weakness class beyond this one, and the vendor. fit-rules@v1

9767 records in this class held. The six above are drawn from the ones CISA has listed as exploited, ranked by how much of the record matches this one. That is why every one of them is KEV-listed: the pool is, so the colour on those spokes says nothing the pool has not already said.

No curated product neighbourhood is held for this product, so the records above are the nearest this index can name. The neighbourhood table covers a small set of products and is extended by hand.

Siblings and hubs

Records related to this one

Its defect family

openssl

Of the 12 records in this family that state one, this holds the highest EPSS percentile: 0.99013.

Grouped by shared product and weakness, not by shared vulnerability. Each record's own state is on its own page.

Family membership: held values

This record is one of a group, and the group's page describes all of them. This page is kept and dated, and the defect family's own page is the one we offer for indexing: the whole group.

Browse the index from here

These are index-wide views, not findings about CVE-2017-3731.

What usually comes next

Everything above needs no account. What is below is work: assembling it, scoping it to your estate, watching it, and handing it to someone else.

Everything on this page is free. Public data. Withholding it protects nothing.