Node v10.16.3 (LTS)

Notable changes

This is a security release.

Node.js, as well as many other implementations of HTTP/2, have been found vulnerable to Denial of Service attacks. See https://github.com/Netflix/security-bulletins/blob/master/advisories/third-party/2019-002.md for more information.

Vulnerabilities fixed:

CVE-2019-9511 “Data Dribble” : The attacker requests a large amount of data from a specified resource over multiple streams. They manipulate window size and stream priority to force the server to queue the data in 1-byte chunks. Depending on how efficiently this data is queued, this can consume excess CPU, memory, or both, potentially leading to a denial of service.

: The attacker requests a large amount of data from a specified resource over multiple streams. They manipulate window size and stream priority to force the server to queue the data in 1-byte chunks. Depending on how efficiently this data is queued, this can consume excess CPU, memory, or both, potentially leading to a denial of service. CVE-2019-9512 “Ping Flood” : The attacker sends continual pings to an HTTP/2 peer, causing the peer to build an internal queue of responses. Depending on how efficiently this data is queued, this can consume excess CPU, memory, or both, potentially leading to a denial of service.

: The attacker sends continual pings to an HTTP/2 peer, causing the peer to build an internal queue of responses. Depending on how efficiently this data is queued, this can consume excess CPU, memory, or both, potentially leading to a denial of service. CVE-2019-9513 “Resource Loop” : The attacker creates multiple request streams and continually shuffles the priority of the streams in a way that causes substantial churn to the priority tree. This can consume excess CPU, potentially leading to a denial of service.

: The attacker creates multiple request streams and continually shuffles the priority of the streams in a way that causes substantial churn to the priority tree. This can consume excess CPU, potentially leading to a denial of service. CVE-2019-9514 “Reset Flood” : The attacker opens a number of streams and sends an invalid request over each stream that should solicit a stream of RST_STREAM frames from the peer. Depending on how the peer queues the RST_STREAM frames, this can consume excess memory, CPU, or both, potentially leading to a denial of service.

: The attacker opens a number of streams and sends an invalid request over each stream that should solicit a stream of RST_STREAM frames from the peer. Depending on how the peer queues the RST_STREAM frames, this can consume excess memory, CPU, or both, potentially leading to a denial of service. CVE-2019-9515 “Settings Flood” : The attacker sends a stream of SETTINGS frames to the peer. Since the RFC requires that the peer reply with one acknowledgement per SETTINGS frame, an empty SETTINGS frame is almost equivalent in behavior to a ping. Depending on how efficiently this data is queued, this can consume excess CPU, memory, or both, potentially leading to a denial of service.

: The attacker sends a stream of SETTINGS frames to the peer. Since the RFC requires that the peer reply with one acknowledgement per SETTINGS frame, an empty SETTINGS frame is almost equivalent in behavior to a ping. Depending on how efficiently this data is queued, this can consume excess CPU, memory, or both, potentially leading to a denial of service. CVE-2019-9516 “0-Length Headers Leak” : The attacker sends a stream of headers with a 0-length header name and 0-length header value, optionally Huffman encoded into 1-byte or greater headers. Some implementations allocate memory for these headers and keep the allocation alive until the session dies. This can consume excess memory, potentially leading to a denial of service.

: The attacker sends a stream of headers with a 0-length header name and 0-length header value, optionally Huffman encoded into 1-byte or greater headers. Some implementations allocate memory for these headers and keep the allocation alive until the session dies. This can consume excess memory, potentially leading to a denial of service. CVE-2019-9517 “Internal Data Buffering” : The attacker opens the HTTP/2 window so the peer can send without constraint; however, they leave the TCP window closed so the peer cannot actually write (many of) the bytes on the wire. The attacker then sends a stream of requests for a large response object. Depending on how the servers queue the responses, this can consume excess memory, CPU, or both, potentially leading to a denial of service.

: The attacker opens the HTTP/2 window so the peer can send without constraint; however, they leave the TCP window closed so the peer cannot actually write (many of) the bytes on the wire. The attacker then sends a stream of requests for a large response object. Depending on how the servers queue the responses, this can consume excess memory, CPU, or both, potentially leading to a denial of service. CVE-2019-9518 “Empty Frames Flood”: The attacker sends a stream of frames with an empty payload and without the end-of-stream flag. These frames can be DATA, HEADERS, CONTINUATION and/or PUSH_PROMISE. The peer spends time processing each frame disproportionate to attack bandwidth. This can consume excess CPU, potentially leading to a denial of service. (Discovered by Piotr Sikora of Google)

Commits

[ 74507fae34 ] - deps : update nghttp2 to 1.39.2 (Anna Henningsen) #29122

] - : update nghttp2 to 1.39.2 (Anna Henningsen) #29122 [ a397c881ec ] - deps : update nghttp2 to 1.39.1 (gengjiawen) #28448

] - : update nghttp2 to 1.39.1 (gengjiawen) #28448 [ fedfa12a33 ] - deps : update nghttp2 to 1.38.0 (gengjiawen) #27295

] - : update nghttp2 to 1.38.0 (gengjiawen) #27295 [ ab0f2ace36 ] - deps : update nghttp2 to 1.37.0 (gengjiawen) #26990

] - : update nghttp2 to 1.37.0 (gengjiawen) #26990 [ 0acbe05ee2 ] - http2 : allow security revert for Ping/Settings Flood (Anna Henningsen) #29122

] - : allow security revert for Ping/Settings Flood (Anna Henningsen) #29122 [ c152449012 ] - http2 : pause input processing if sending output (Anna Henningsen) #29122

] - : pause input processing if sending output (Anna Henningsen) #29122 [ 0ce699c7b1 ] - http2 : stop reading from socket if writes are in progress (Anna Henningsen) #29122

] - : stop reading from socket if writes are in progress (Anna Henningsen) #29122 [ 17357d37a9 ] - http2 : consider 0-length non-end DATA frames an error (Anna Henningsen) #29122

] - : consider 0-length non-end DATA frames an error (Anna Henningsen) #29122 [ 460f896c63 ] - http2 : shrink default vector::reserve() allocations (Anna Henningsen) #29122

] - : shrink default allocations (Anna Henningsen) #29122 [ f4242e24f9 ] - http2 : handle 0-length headers better (Anna Henningsen) #29122

] - : handle 0-length headers better (Anna Henningsen) #29122 [ 477461a51f ] - http2 : limit number of invalid incoming frames (Anna Henningsen) #29122

] - : limit number of invalid incoming frames (Anna Henningsen) #29122 [ 05dada46ee ] - http2 : limit number of rejected stream openings (Anna Henningsen) #29122

] - : limit number of rejected stream openings (Anna Henningsen) #29122 [ 7f11465572 ] - http2 : do not create ArrayBuffers when no DATA received (Anna Henningsen) #29122

] - : do not create ArrayBuffers when no DATA received (Anna Henningsen) #29122 [ 2eb914ff5f ] - http2 : only call into JS when necessary for session events (Anna Henningsen) #29122

] - : only call into JS when necessary for session events (Anna Henningsen) #29122 [ 76a7ada15d ] - http2 : improve JS-side debug logging (Anna Henningsen) #29122

] - : improve JS-side debug logging (Anna Henningsen) #29122 [ 00f153da13 ] - http2 : improve http2 code a bit (James M Snell) #23984

] - : improve http2 code a bit (James M Snell) #23984 [ a0a14c809f ] - src : pass along errors from http2 object creation (Anna Henningsen) #25822

] - : pass along errors from http2 object creation (Anna Henningsen) #25822 [ d85e4006ab ] - test: apply test-http2-max-session-memory-leak from v12.x (Anna Henningsen) #29122

Windows 32-bit Installer: https://nodejs.org/dist/v10.16.3/node-v10.16.3-x86.msi

Windows 64-bit Installer: https://nodejs.org/dist/v10.16.3/node-v10.16.3-x64.msi

Windows 32-bit Binary: https://nodejs.org/dist/v10.16.3/win-x86/node.exe

Windows 64-bit Binary: https://nodejs.org/dist/v10.16.3/win-x64/node.exe

macOS 64-bit Installer: https://nodejs.org/dist/v10.16.3/node-v10.16.3.pkg

macOS 64-bit Binary: https://nodejs.org/dist/v10.16.3/node-v10.16.3-darwin-x64.tar.gz

Linux 64-bit Binary: https://nodejs.org/dist/v10.16.3/node-v10.16.3-linux-x64.tar.xz

Linux PPC LE 64-bit Binary: https://nodejs.org/dist/v10.16.3/node-v10.16.3-linux-ppc64le.tar.xz

Linux s390x 64-bit Binary: https://nodejs.org/dist/v10.16.3/node-v10.16.3-linux-s390x.tar.xz

AIX 64-bit Binary: https://nodejs.org/dist/v10.16.3/node-v10.16.3-aix-ppc64.tar.gz

SmartOS 64-bit Binary: https://nodejs.org/dist/v10.16.3/node-v10.16.3-sunos-x64.tar.xz

ARMv6 32-bit Binary: https://nodejs.org/dist/v10.16.3/node-v10.16.3-linux-armv6l.tar.xz

ARMv7 32-bit Binary: https://nodejs.org/dist/v10.16.3/node-v10.16.3-linux-armv7l.tar.xz

ARMv8 64-bit Binary: https://nodejs.org/dist/v10.16.3/node-v10.16.3-linux-arm64.tar.xz

Source Code: https://nodejs.org/dist/v10.16.3/node-v10.16.3.tar.gz

Other release files: https://nodejs.org/dist/v10.16.3/

Documentation: https://nodejs.org/docs/v10.16.3/api/

SHASUMS