CVE-2017-15896
Last modified
CVE-2017-15896 is a critical-severity vulnerability rated 9.1/10 on the CVSS scale. 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.. EPSS estimates a 2.38% chance of exploitation in the next 30 days.
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.
Metrics
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Nodejs | Node.Js | >= 4.0.0, <= 4.1.2 |
| Nodejs | Node.Js | >= 4.2.0, < 4.8.7 |
| Nodejs | Node.Js | >= 6.0.0, <= 6.8.1 |
| Nodejs | Node.Js | >= 6.9.0, < 6.12.2 |
| Nodejs | Node.Js | >= 8.0.0, <= 8.8.1 |
| Nodejs | Node.Js | >= 8.9.0, < 8.9.3 |
| Nodejs | Node.Js | >= 9.0.0, < 9.2.1 |
References
- https://nodejs.org/en/blog/vulnerability/december-2017-security-releases/Issue Tracking, Vendor Advisory
- https://nodejs.org/en/blog/vulnerability/december-2017-security-releases/Issue Tracking, Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2017-15896?
How severe is CVE-2017-15896?
How do I fix CVE-2017-15896?
Are you affected by CVE-2017-15896?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
