vciy

CVE-2017-3738

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.

There is an overflow bug in the AVX2 Montgomery multiplication procedure used in exponentiation with 1024-bit moduli

CVE-2017-37384 of 4 sources documented this
29

rank 29 = 3 + 15 + 1 + 10 + 0

rank@v1 · scheduled

Someone is already using it

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

EPSS 0.13411  ·  without this subject the record ranks 26

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 5.9, from NVD  ·  without this subject the record ranks 14

It is getting worse, not staying still

FIRST EPSS series, rescorings and bad loads removed

rose on 2025-10-04  ·  without this subject the record ranks 28

How much of the world it touches

NVD CPE configurations

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

Someone else already set the date

CISA KEV remediation due date

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

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$410,000over the next 30 days, if this record is yours
Movement+$134,000on 2026-03-04, the last material move, 3 months before this reading
Basisassumeda published average, not your estate

$410,000 = $4.99M incident cost x 0.6121449559255632 exposure x 0.13411 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.13411EPSSNOT IN KEVas of 2026-09-20
Severity5.9 MEDIUMreceipt
Harmunauthenticated · networkreceipt
Exploitationnone in held sources
Defenseno fix version held
Movementscoring model changedreceipt
PLATEAU10Minimal movement since 2025-03-17, 455 days at 0.13, as of 2026-06-15. arc-rules@v1

Foresight · where to check next

Fortinet FortiOSCVE-2016-6415Cisco Adaptivevitejs viteminioCVE-2016-23883738

This record is one instance of CWE-200, exposure of sensitive information to an unauthorized actor. The index holds 11146 prior instances of this class, 18 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 · high attack complexityreceipt
ImpactComplete confidentiality lossreceipt
Scored fromCVSS v3.1 · NVD's vectorreceipt
Weakness classCWE-200 Exposure of Sensitive Information to an Unauthorized Actorreceipt
Published consequencesCWE-200: Confidentiality: Read Application Data[email protected]

CISA KEV & Federal Remediation Deadline from the record and CISA

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

Fixed inNo fix version in held sources, as the index stood on 15 Jun 2026.
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, NVD5.9 MEDIUMreceipt
Exploit probability0.13411 · top 4% of all CVEsreceipt
Blast breadth1 product across 1 vendorderived
Assigned byopensslreceipt
Recorded changes57 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Affected productOpenSSL Software Foundation OpenSSLreceipt
Published rangesopenssl 1.0.2; openssl 1.0.2a; openssl 1.0.2b; openssl 1.0.2creceipt
Show all 20 published ranges
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.2g
openssl 1.0.2h
openssl 1.0.2i
openssl 1.0.2j
openssl 1.0.2k
openssl 1.0.2l
openssl 1.0.2m
openssl 1.1.0
openssl 1.1.0a
openssl 1.1.0b
openssl 1.1.0c
openssl 1.1.0d
openssl 1.1.0e

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

There is an overflow bug in the AVX2 Montgomery multiplication procedure used in exponentiation with 1024-bit moduli. No EC algorithms are affected. Analysis suggests that attacks against RSA and DSA as a result of this defect would be very difficult to perform and are not believed likely. Attacks against DH1024 are considered just feasible, because most of the work necessary to deduce information about a private key may be performed offline. The amount of resources required for such an attack would be significant. However, for an attack on TLS to be meaningful, the server would have to share the DH1024 private key among multiple clients, which is no longer an option since CVE-2016-0701. receipt

Read the rest of the CNA's description

This only affects processors that support the AVX2 but not ADX extensions like Intel Haswell (4th generation). Note: The impact from this issue is similar to CVE-2017-3736, CVE-2017-3732 and CVE-2015-3193. OpenSSL version 1.0.2-1.0.2m and 1.1.0-1.1.0g are affected. Fixed in OpenSSL 1.0.2n. Due to the low severity of this issue we are not issuing a new release of OpenSSL 1.1.0 at this time. The fix will be included in OpenSSL 1.1.0h when it becomes available. The fix is also available in commit e502cc86d in the OpenSSL git repository.

NVD's analysis a second authority

severity
5.9 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
weakness
CWE-200
affected versions
openssl 1.0.2; openssl 1.0.2a; openssl 1.0.2b; and 17 more, listed in full below

check it yourself tenable.com tenable.com access.redhat.com access.redhat.com oracle.com oracle.com +14 morereceipt

Dated events

2025-03-17EPSS moved 0.01 to 0.162026-03-04EPSS moved 0.10 to 0.14

Movement the material steps

14 Apr 20210.05624
7 Mar 20230.00764 · scoring model v2023.03.01
17 Mar 20250.16379 · crossed 0.10 · scoring model v2025.03.14
1 Aug 20250.09427 · crossed 0.10
4 Aug 20250.12324 · crossed 0.10
1 Sep 20250.09427 · crossed 0.10
4 Sep 20250.12324 · crossed 0.10
1 Oct 20250.09873 · crossed 0.10
4 Oct 20250.14389 · crossed 0.10
1 Nov 20250.0956 · crossed 0.10
4 Nov 20250.13961 · crossed 0.10
1 Dec 20250.09794 · crossed 0.10
4 Dec 20250.14281 · crossed 0.10
1 Jan 20260.0956 · crossed 0.10
4 Jan 20260.13961 · crossed 0.10
1 Feb 20260.0956 · crossed 0.10
4 Feb 20260.13961 · crossed 0.10
1 Mar 20260.0956 · crossed 0.10
4 Mar 20260.13961 · crossed 0.10
15 Jun 20260.13411 · scoring model v2026.06.15
Show all 57 observations
14 Apr 20210.05624
4 Feb 20220.0472
7 Mar 20230.00764
30 Apr 20230.00832
8 May 20230.01221
9 Jun 20230.01039
3 Jul 20230.00817
2 Feb 20240.00758
12 Mar 20240.00768
17 Dec 20240.01456
17 Mar 20250.16379
29 Mar 20250.17577
30 Mar 20250.16379
3 Apr 20250.20744
27 Apr 20250.17587
1 May 20250.11761
4 May 20250.17587
1 Jun 20250.11761
4 Jun 20250.17587
23 Jun 20250.19618
1 Jul 20250.13254
4 Jul 20250.19618
6 Jul 20250.18576
10 Jul 20250.14563
30 Jul 20250.12324
1 Aug 20250.09427
4 Aug 20250.12324
1 Sep 20250.09427
4 Sep 20250.12324
16 Sep 20250.12172
1 Oct 20250.09873
4 Oct 20250.14389
5 Oct 20250.13961
27 Oct 20250.11799
28 Oct 20250.13961
1 Nov 20250.0956
4 Nov 20250.13961
7 Nov 20250.14281
1 Dec 20250.09794
4 Dec 20250.14281
8 Dec 20250.15668
9 Dec 20250.14281
12 Dec 20250.13961
27 Dec 20250.11799
28 Dec 20250.13961
1 Jan 20260.0956
4 Jan 20260.13961
1 Feb 20260.0956
4 Feb 20260.13961
1 Mar 20260.0956
4 Mar 20260.13961
18 Mar 20260.17287
22 Mar 20260.13495
28 Mar 20260.17287
8 Apr 20260.1413
9 Apr 20260.15507
15 Jun 20260.13411

57 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.13411Published2017-12-07Index as of2026-06-15

The record had been public for 8 years, 6 months when this index was last written.

Published 2017-12-07 receipt · Index as of 2026-06-15 derived

The pattern, elsewhere

This record is one instance of CWE-200, exposure of sensitive information to an unauthorized actor. The index holds 11146 prior instances of this class, 18 KEV-listed. The nearest of its KEV-listed records are drawn beside this. [email protected]

CVE-2025-68686 · Fortinet FortiOSmatches 8 of 9KEV listed · 2026receipt
CVE-2016-6415matches 7 of 8KEV listed · 2016receipt
CVE-2020-3259 · Cisco Adaptive Security Appliance (ASA)…matches 7 of 9KEV listed · 2020receipt
CVE-2025-31125 · vitejs vitematches 7 of 9KEV listed · 2025receipt
CVE-2023-28432 · miniomatches 7 of 9KEV listed · 2023receipt
CVE-2016-2388matches 6 of 8KEV listed · 2016receipt

"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

11146 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 software foundation openssl

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

Family membership: held values

Nothing we hold separates this record from the others in its defect family. 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-3738.

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.