CVE-2017-15896

CRITICAL
9.1
CVSS Score
Published: December 11, 2017 at 09:00 PM UTC
Updated: June 17, 2026 at 01:08 AM UTC
1 product affected across 1 vendorNode.js

Using Node.js by The Node.js Project?

Get instant alerts when new vulnerabilities affect Node.js - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
CRITICAL9.1
Exploit prediction
EPSS 2%

Description

Node.js was affected by OpenSSL vulnerability CVE-2017-3737 in regards to the use of SSL_read() due to TLS handshake failure. The result was that an active network attacker could send application data to Node.js using the TLS or HTTP2 modules in a way that bypassed TLS authentication and encryption.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v ≥ 4.0.0v ≥ 6.0.0v ≥ 8.0.0v ≥ 9.0.04.0.0 ≤ v ≤ 4.1.24.2.0 ≤ v < 4.8.76.0.0 ≤ v ≤ 6.8.16.9.0 ≤ v < 6.12.28.0.0 ≤ v ≤ 8.8.18.9.0 ≤ v < 8.9.39.0.0 ≤ v < 9.2.1
Affected range stops below 4.8.7, so it looks safe — our inference, not a vendor statement
Affected range stops below 6.12.2, so it looks safe — our inference, not a vendor statement
Affected range stops below 8.9.3, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.2.1, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (1)

CVSS

Attack Vector
NETWORK
Complexity
LOW
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
HIGH
Availability
NONE
Vector?

Quick Info

StatusMODIFIED
CWE
NVD-CWE-noinfo

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card