(Update 7-December-2017) Security releases available
Updates are now available for all active Node.js release lines. These include the fix for the vulnerability identified in the initial announcement.
In addition the updates for 8.X and 9.X include a fix for a low severity buffer vulnerability as describe below.
We recommend that all users upgrade as soon as possible.
Data Confidentiality/Integrity Vulnerability – CVE-2017-15896
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.
The original HTTP module was not affected.
The vulnerability in the HTTP2 module (which only existing in the 8.X and 9.X lines) was fixed through nodejs/node@f3686f2. HTTP2 was previously exploitable through the submission of malicious data by an attacker.
The vulnerability in the TLS module was fixed by incorporating OpenSSL-1.0.2n into Node.js. We are not currently aware of any exploits but it was previously at a severe security risk of accepting unauthenticated data. See this advisory from OpenSSL for more details on the fixes in OpenSSL-1.0.2n secadv-20171207.txt.
The HTTPS module was not affected.
This vulnerability has been assigned CVE-2017-15896.
We would like to thank Matt Caswell (OpenSSL) and David Benjamin (Google) for reporting this.
Uninitialized buffer vulnerability – CVE-2017-15897
Node.js had a bug in versions 8.X and 9.X which caused buffers to not be initialized when the encoding for the fill value did not match the encoding specified. For example, ‘Buffer.alloc(0x100, “This is not correctly encoded”, “hex”);’ The buffer implementation was updated such that the buffer will be initialized to all zeros in these cases.
Versions 4.X and 6.X were not vulnerable.
The severity of this information disclosure vulnerability was low (due to the combination of coding errors that need to have been made in order to make it exploitable) and it has been assigned CVE-2017-15897.
Also included in OpenSSL update – CVE 2017-3738
Note that CVE 2017-3738 of OpenSSL-1.0.2 affected Node but it was low severity as described in secadv-20171207.txt.
Original post is included below
The Node.js project will be releasing new versions of 4.x, 6.x, 8.x and 9.x as soon as possible after the OpenSSL release, on or soon after December 8th UTC, to incorporate a security fix.
Data Confidentiality/Integrity Vulnerability
All versions of 4.x, 6.x, 8.x and 9.x are vulnerable to an issue to be fixed in the forthcoming OpenSSL-1.0.2n released on Dec 7, see https://mta.openssl.org/pipermail/openssl-announce/2017-December/000108.html for more details. The severity of this vulnerability of Node.js is HIGH (due to the way Node.js uses the OpenSSL APIs) and users of the affected versions should plan to upgrade when a fix is made available.
- Versions 4.0 and later of Node.js are vulnerable
- Versions 6.0 and later of Node.js are vulnerable
- Versions 8.0 and later of Node.js are vulnerable
- Versions 9.0 and later of Node.js are vulnerable
Releases will be available as soon as possible after the OpenSSL release, along with disclosure of the details for the vulnerability in order to allow for complete impact assessment by users.
Contact and future updates
The current Node.js security policy can be found at https://nodejs.org/en/security/.
Please contact email@example.com if you wish to report a vulnerability in Node.js.
Subscribe to the low-volume announcement-only nodejs-sec mailing list at https://groups.google.com/forum/#!forum/nodejs-sec to stay up to date on security vulnerabilities and security-related releases of Node.js and the projects maintained in the nodejs GitHub organisation.