Node.js 4 4.6.0
Node.js 4 4.6.0, released September 27, 2016, fixes 8 CVEs in Node.js 4. None of them is reported as exploited. Patch Radar priority: Urgent. The latest Node.js 4 is 4.8.7, which also fixes every one of these CVEs.
Superseded. The latest Node.js 4 is 4.8.7, which also fixes every CVE on this page. Install that instead.
Priority of the 8 CVEs
Applies to
| Product | Version |
|---|---|
| Node.js 4 | 4.6.0 |
CVEs this fix closes
| Priority | CVE | Title | CVSS | EPSS | Exploitation |
|---|---|---|---|---|---|
| Urgent | CVE-2016-6303 | Node.js 4: Integer overflow in the MDC2_Update function in crypto/mdc2/mdc2dgst.c in OpenSSL before 1.1.0 allows… | 9.8 | 0.3199 | None reported |
| High | CVE-2016-2183 | Node.js 4 and 1 other: Exposure of Sensitive Information to an Unauthorized Actor | 7.5 | 0.9470 | None reported |
| High | CVE-2016-6304 | Node.js 4: Multiple memory leaks in t1_lib.c in OpenSSL before 1.0.1u, 1.0.2 before 1.0.2i, and 1.1.0 before 1.1.0a… | 7.5 | 0.6303 | None reported |
| High | CVE-2016-7052 | Node.js 4: crypto/x509/x509_vfy.c in OpenSSL 1.0.2i allows remote attackers to cause a denial of service (NULL pointer… | 7.5 | 0.2946 | None reported |
| Routine | CVE-2016-6306 | Node.js 4: The certificate parser in OpenSSL before 1.0.1u and 1.0.2 before 1.0.2i might allow remote attackers… | 5.9 | 0.4168 | None reported |
| Routine | CVE-2016-5325 | Node.js 4: CRLF injection vulnerability in the ServerResponse#writeHead function in Node.js 0.10.x before 0.10.47,… | 6.1 | 0.0409 | None reported |
| Routine | CVE-2016-7099 | Node.js 4: The tls.checkServerIdentity function in Node.js 0.10.x before 0.10.47, 0.12.x before 0.12.16, 4.x before… | 5.9 | 0.0284 | None reported |
| Routine | CVE-2016-2178 | Node.js 4: The dsa_sign_setup function in crypto/dsa/dsa_ossl.c in OpenSSL through 1.0.2h does not properly ensure… | 5.5 | 0.0124 | None reported |
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.