Version 8.16.2 'Carbon' (LTS):
Notable changes
deps: upgrade openssl sources to 1.0.2s
Version 8.16.1 'Carbon' (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.
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.
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.
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.
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.
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.
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.
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.
Version 8.16.0 'Carbon' (LTS):
Notable Changes
n-api:
add API for asynchronous functions
mark thread-safe function as stable
- async_hooks:
- rename PromiseWrap.parentId
- remove runtime deprecation
- deprecate unsafe emit{Before,After}
- cluster:
- add cwd to cluster.settings
- support windowsHide option for workers
- crypto:
- allow passing null as IV unless required
- deps:
- upgrade npm to 6.4.1
- upgrade libuv to 1.19.2
- Upgrade node-inspect to 1.11.5
- fs,net:
- support as and as+ flags in stringToFlags()
- emit 'ready' for fs streams and sockets
- http, http2:
- add options to http.createServer()
- add 103 Early Hints status code
- add http fallback options to .createServer
- n-api:
- take n-api out of experimental
- perf_hooks:
- add warning when too many entries in the timeline
- src:
- add public API for managing NodePlatform
- allow --perf-(basic-)?prof in NODE\_OPTIONS
- node internals' postmortem metadata
- tls:
- expose Finished messages in TLSSocket
- trace_events:
- add file pattern cli option
- util:
- implement util.getSystemErrorName()
deps:
- update V8 to 6.2.414.46
- revert ABI breaking changes in V8 6.2
- upgrade libuv to 1.19.1
- re land npm 5.6.0
- ICU 60 bump
crypto:
- Support both OpenSSL 1.1.0 and 1.0.2
- warn on invalid authentication tag length
async_hooks:
- update defaultTriggerAsyncIdScope for perf
- use typed array stack as fast path
- use scope for defaultTriggerAsyncId
- separate missing from default context
- rename initTriggerId
- deprecate undocumented API
- add destroy event for gced AsyncResources
- add trace events to async_hooks
- set HTTPParser trigger to socket
- add provider types for net server
n-api:
- add helper for addons to get the event loop
cli:
- add --stack-trace-limit to NODE_OPTIONS
console:
- add support for console.debug
module:
- add builtinModules
- replace default paths in require.resolve()
src:
- add helper for addons to get the event loop
- add process.ppid
http:
- support generic `Duplex` streams
- add rawPacket in err of `clientError` event
- better support for IPv6 addresses
net:
- remove ADDRCONFIG DNS hint on Windows
process:
- fix reading zero-length env vars on win32
tls:
- unconsume stream on destroy
process:
- improve unhandled rejection message
stream:
- remove usage of *State.highWaterMark
trace_events:
- add executionAsyncId to init events
Changes since nodejs 8.8.1:
- doc: add Gibson Fahnestock to Release team
- deps: update npm to 5.5.1
- http2: The exposed http2 socket is no longer manipulatable
- module: support custom paths to require.resolve()
- util: util.TextEncoder and util.TextDecoder are no longer experimental.
There will no longer be a warning when they are used
