This repository has been archived by the owner on Apr 17, 2023. It is now read-only.
fix(deps): update dependency ws to v7.4.6 [security] #304
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:
7.3.0
->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
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
).Configuration
📅 Schedule: Branch creation - "" (UTC), 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 these updates again.
This PR has been generated by Mend Renovate. View repository job log here.