CVE-2017-15896

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.

9.1

CVSS

Severity: Critical

CVSS 3.1 •

CVSS 2.0 •

EPSS 0.10%

Vendor Advisory nodejs.org

Affected: The Node.js Project Node.js

References

Link	Tags
https://nodejs.org/en/blog/vulnerability/december-2017-security-releases/	issue tracking vendor advisory

Frequently Asked Questions

What is the severity of CVE-2017-15896?: CVE-2017-15896 has been scored as a critical severity vulnerability.
How to fix CVE-2017-15896?: To fix CVE-2017-15896, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2017-15896 being actively exploited in the wild?: As for now, there are no information to confirm that CVE-2017-15896 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2017-15896?: CVE-2017-15896 affects The Node.js Project Node.js.

This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.