Skip to content

chore(deps): update node.js #75

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

chore(deps): update node.js #75

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Nov 20, 2018 •
edited
Loading

This PR contains the following updates:

Package Type Update Change
circleci/node docker minor 8.12.0 -> 8.17.0
node minor 8.12.0 -> 8.17.0

Release Notes

nodejs/node

v8.17.0

Compare Source

This is a security release.

For more details about the vulnerability please consult the npm blog:

https://blog.npmjs.org/post/189618601100/binary-planting-with-the-npm-cli

Notable changes
Commits

v8.16.2

Compare Source

Node.js 8 is due to go End-of-Life on 31st December 2019.

Notable changes
  • deps: upgrade openssl sources to 1.0.2s (Sam Roberts) #​28230
Commits

v8.16.1

Compare Source

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. (Discovered by Piotr Sikora of Google)
Commits

v8.16.0

Compare Source

Notable Changes
  • n-api:
    • add API for asynchronous functions (Gabriel Schulhof) #​17887
    • mark thread-safe function as stable (Gabriel Schulhof) #​25556
Commits

v8.15.1

Compare Source

v8.15.0

Compare Source

The 8.14.0 security release introduced some unexpected breakages on the 8.x release line.
This is a special release to fix a regression in the HTTP binary upgrade response body and add
a missing CLI flag to adjust the max header size of the http parser.

Notable Changes
  • cli:
    • add --max-http-header-size flag (cjihrig) #​24811
  • http:
    • add maxHeaderSize property (cjihrig) #​24860
Commits

v8.14.1

Compare Source

Notable changes
  • assert:
    • revert breaking change (Ruben Bridgewater) #​24786
  • http2:
    • fix sequence of error/close events (Gerhard Stoebich) #​24789
Commits

v8.14.0

Compare Source

This is a security release. All Node.js users should consult the security release summary at:

https://nodejs.org/en/blog/vulnerability/november-2018-security-releases/

for details on patched vulnerabilities.

Fixes for the following CVEs are included in this release:

  • Node.js: Denial of Service with large HTTP headers (CVE-2018-12121)
  • Node.js: Slowloris HTTP Denial of Service (CVE-2018-12122 / Node.js)
  • Node.js: Hostname spoofing in URL parser for javascript protocol (CVE-2018-12123)
  • Node.js: HTTP request splitting (CVE-2018-12116)
  • OpenSSL: Timing vulnerability in DSA signature generation (CVE-2018-0734)
  • OpenSSL: Microarchitecture timing vulnerability in ECC scalar multiplication (CVE-2018-5407)
Notable Changes
  • deps: Upgrade to OpenSSL 1.0.2q, fixing CVE-2018-0734 and CVE-2018-5407
  • http:
    • Headers received by HTTP servers must not exceed 8192 bytes in total to prevent possible Denial of Service attacks. Reported by Trevor Norris. (CVE-2018-12121 / Matteo Collina)
    • A timeout of 40 seconds now applies to servers receiving HTTP headers. This value can be adjusted with server.headersTimeout. Where headers are not completely received within this period, the socket is destroyed on the next received chunk. In conjunction with server.setTimeout(), this aids in protecting against excessive resource retention and possible Denial of Service. Reported by Jan Maybach (liebdich.com). (CVE-2018-12122 / Matteo Collina)
    • Two-byte characters are now strictly disallowed for the path option in HTTP client requests. Paths containing characters outside of the range \u0021 - \u00ff will now be rejected with a TypeError. This behavior can be reverted if necessary by supplying the --security-revert=CVE-2018-12116 command line argument (this is not recommended). Reported as security concern for Node.js 6 and 8 by Arkadiy Tetelman (Lob), fixed by backporting a change by Benno Fünfstück applied to Node.js 10 and later. (CVE-2018-12116 / Matteo Collina)
  • url: Fix a bug that would allow a hostname being spoofed when parsing URLs with url.parse() with the 'javascript:' protocol. Reported by Martin Bajanik (Kentico). (CVE-2018-12123 / Matteo Collina)
Commits

v8.13.0

Compare Source

Notable changes
  • assert:
    • backport some assert commits (Ruben Bridgewater) #​23223
  • deps:
    • upgrade to libuv 1.23.2 (cjihrig) #​23336
    • V8: cherry-pick 64-bit hash seed commits (Yang Guo) #​23274
  • http:
    • added aborted property to request (Robert Nagy) #​20094
  • http2:
    • graduate from experimental (James M Snell) #​22466
Commits

Renovate configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻️ Rebasing: Whenever PR becomes conflicted, or if you modify the PR title to begin with "rebase!".

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

  • If you want to rebase/retry this PR, check this box

Newsflash: Renovate has joined WhiteSource, and is now free for all use. Learn more or view updated terms and privacy policies.
@renovate renovate bot force-pushed the renovate/node-8.x branch from e50e3eb to 99d2b0b Compare November 27, 2018 23:03
@renovate renovate bot changed the title chore(deps): update node.js to v8.13.0 Nov 28, 2018
@renovate renovate bot force-pushed the renovate/node-8.x branch 2 times, most recently from f41101b to 43c5ede Compare November 28, 2018 22:42
@renovate renovate bot changed the title chore(deps): update node.js Nov 28, 2018
@renovate renovate bot force-pushed the renovate/node-8.x branch 8 times, most recently from 72723a2 to 73a97a8 Compare December 6, 2018 00:39
@renovate renovate bot force-pushed the renovate/node-8.x branch 7 times, most recently from 44351b2 to 75d2b9e Compare December 13, 2018 01:00
@renovate renovate bot force-pushed the renovate/node-8.x branch 8 times, most recently from 3f19859 to ec3e50f Compare December 18, 2018 16:40
@renovate renovate bot changed the title chore(deps): update node.js to v8.14.0 Dec 18, 2018
@renovate renovate bot force-pushed the renovate/node-8.x branch from ec3e50f to 87d97ac Compare December 19, 2018 00:45
@renovate renovate bot force-pushed the renovate/node-8.x branch 11 times, most recently from 52e0323 to 616bb39 Compare April 12, 2019 00:46
@renovate renovate bot force-pushed the renovate/node-8.x branch from 616bb39 to b18d7bc Compare April 23, 2019 23:00
@renovate renovate bot force-pushed the renovate/node-8.x branch from b18d7bc to 55f1e4a Compare May 4, 2019 16:52
@renovate renovate bot force-pushed the renovate/node-8.x branch 2 times, most recently from 28fdac3 to a09a684 Compare May 19, 2019 03:57
@renovate renovate bot force-pushed the renovate/node-8.x branch 2 times, most recently from c67cff1 to e18b1cf Compare May 25, 2019 17:48
@renovate renovate bot force-pushed the renovate/node-8.x branch from e18b1cf to 14e4b1f Compare June 1, 2019 09:52
@renovate renovate bot force-pushed the renovate/node-8.x branch from 14e4b1f to 34e2b95 Compare June 19, 2019 13:53
@renovate renovate bot force-pushed the renovate/node-8.x branch from 34e2b95 to bbf389f Compare July 13, 2019 14:59
@renovate renovate bot force-pushed the renovate/node-8.x branch from bbf389f to 66cdfd8 Compare August 10, 2019 08:57
@renovate renovate bot force-pushed the renovate/node-8.x branch from 66cdfd8 to d0eee5f Compare August 23, 2019 08:55
@renovate renovate bot force-pushed the renovate/node-8.x branch 2 times, most recently from 91472de to ee2765b Compare September 7, 2019 16:55
@renovate renovate bot force-pushed the renovate/node-8.x branch from ee2765b to 4707ee3 Compare October 4, 2019 12:54
@renovate renovate bot force-pushed the renovate/node-8.x branch from 4707ee3 to c96d29e Compare November 11, 2019 14:57
@renovate renovate bot force-pushed the renovate/node-8.x branch from c96d29e to 5a9f9f3 Compare November 21, 2019 10:14
@renovate renovate bot force-pushed the renovate/node-8.x branch from 5a9f9f3 to 1a8e9de Compare December 14, 2019 22:52
@renovate renovate bot force-pushed the renovate/node-8.x branch from 1a8e9de to 311ccb7 Compare December 22, 2019 04:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
1 participant
@renovate-bot