chore(deps): update dependency ws to v7 [security] #30288
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
5.2.4
->7.4.6
GitHub Vulnerability Alerts
CVE-2021-32640
Impact
A specially crafted value of the
Sec-Websocket-Protocol
header can be used to significantly slow down a ws server.Proof of concept
Patches
The vulnerability was fixed in [email protected] (websockets/ws@00c425e) and backported to [email protected] (websockets/ws@78c676d) and [email protected] (websockets/ws@76d47c1).
Workarounds
In vulnerable versions of ws, the issue can be mitigated by reducing the maximum allowed length of the request headers using the
--max-http-header-size=size
and/or themaxHeaderSize
options.Credits
The vulnerability was responsibly disclosed along with a fix in private by Robert McLaughlin from University of California, Santa Barbara.
Release Notes
websockets/ws (ws)
v7.4.6
Compare Source
Bug fixes
00c425e
).A specially crafted value of the
Sec-Websocket-Protocol
header could be usedto significantly slow down a ws server.
The vulnerability was responsibly disclosed along with a fix in private by
Robert McLaughlin from University of California, Santa Barbara.
In vulnerable versions of ws, the issue can be mitigated by reducing the maximum
allowed length of the request headers using the
--max-http-header-size=size
and/or the
maxHeaderSize
options.v7.4.5
Compare Source
Bug fixes
utf-8-validate
is not installed(
23ba6b2
).websocket.close()
andwebsocket.terminate()
didnot close the connection (
67e25ff
).v7.4.4
Compare Source
Bug fixes
permessage-deflate extension (
9277437
).v7.4.3
Compare Source
Bug fixes
takeover is disabled (#1840).
v7.4.2
Compare Source
Bug fixes
a2c0d44
).v7.4.1
Compare Source
Bug fixes
'error'
event bug in Node.js < 13 whichcaused an uncaught error during the WebSocket handshake (
38d6ab3
).v7.4.0
Compare Source
Features
WebSocketServer.prototype.handleUpgrade()
now takes theclient HTTP GET request as second argument (
7d39f19
).Bug fixes
eabed8f
).CONNECTING
,OPEN
,CLOSING
,CLOSED
,binaryType
,bufferedAmount
,extensions
,onclose
,onerror
,onmessage
,onopen
,protocol
,readyState
, andurl
properties are now enumerable (2069e68
).v7.3.1
Compare Source
Bug fixes
websocket.bufferedAmount
accuracy (e1349c0
,a162942
).v7.3.0
Compare Source
Features
WebSocket.prototype.addEventListener()
now supports theonce
option (#1754).v7.2.5
Compare Source
Bug fixes
651d662
).v7.2.3
Compare Source
Bug fixes
WebSocket#{p{i,o}ng,close}()
now thow an error if the data to send is toolarge to fit in a control frame (
e54f08d
).v7.2.2
Compare Source
Bug fixes
webSocketStream.end()
could cause the processto crash (
9535702
).or a masked frame is received on the client (#1681).
v7.2.1
Compare Source
Bug fixes
bufferutil
andutf-8-validate
as peer dependencies (#1626).v7.2.0
Compare Source
Features
readableObjectMode
option when usingWebSocket.createWebSocketStream()
(#1647).v7.1.2
Compare Source
Bug fixes
(#1618).
v7.1.1
Compare Source
Bug fixes
WebSocket
server constructor is usedincorrectly (
3641266
).v7.1.0
Compare Source
Features
WebSocket
in aDuplex
stream (#1589).Bug fixes
if
statement" (dbacf58
, #1591).v7.0.1
Compare Source
Bug fixes
v7.0.0
Compare Source
Breaking changes
1e6999b
).url.Url
instances in theWebSocket
constructor(
692d7b4
).WebSocket#{p{i,o}ng,send}()
has changed when thereadyState
attribute is notOPEN
(#1532)CONNECTING
, an exception is thrown.CLOSING
orCLOSED
bufferedAmount
attribute is increased by the length of thedata
argument in bytes.
callback
function is called with an error.callback
function is not provided.v6.2.3
Compare Source
Bug fixes
e55e510
to the 6.x release line (eeb76d3
).v6.2.2
Compare Source
Bug fixes
00c425e
to the 6.x release line (78c676d
).v6.2.1
Compare Source
Bug fixes
being set (
aa1dcd5
).v6.2.0
Compare Source
Features
Bug fixes
Sec-WebSocket-Key
header fieldvalue is invalid (
160af45
).v6.1.4
Compare Source
Bug fixes
Host
header to always include a port (#1510).v6.1.3
Compare Source
Bug fixes
being parsed (#1494).
v6.1.2
Compare Source
Bug fixes
26436e0
).v6.1.1
Compare Source
Bug fixes
and the socket closes prematurely (#1464, #1471).
v6.1.0
Compare Source
Features
'close'
event when the servercloses (#1453).
v6.0.0
Compare Source
Breaking changes
d73885c
).browser (#1345).
maxPayload
option on the client. Defaults to 100 MiB (#1402).memLevel
andlevel
options. UsezlibDeflateOptions
instead. (80e2002
).Configuration
📅 Schedule: Branch creation - "" in timezone America/New_York, Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.