[Snyk] Upgrade ws from 7.4.6 to 7.5.3 #322
Open
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.
Snyk has created this PR to upgrade ws from 7.4.6 to 7.5.3.
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
Release notes
Package name: ws
-
7.5.3 - 2021-07-10
- The
- Fixed a bug where a
- Fixed a bug that allowed WebSocket connections to be established after
-
7.5.2 - 2021-07-04
- The opening handshake is now aborted if the client receives a
-
7.5.1 - 2021-06-29
- Fixed an issue that prevented the connection from being closed properly if an
-
7.5.0 - 2021-06-16
- Some errors now have a
- A close frame is now sent to the remote peer if an error (such as a data
- The close code is now always 1006 if no close frame is received, even if the
-
7.4.6 - 2021-05-25
- Fixed a ReDoS vulnerability (00c425e).
for (const length of [1000, 2000, 4000, 8000, 16000, 32000]) {
from ws GitHub release notesBug fixes
WebSocketServerconstructor now throws an error if more than one of thenoServer,server, andportoptions are specefied (66e58d2).'close'event was emitted by aWebSocketServerbeforethe internal HTTP/S server was actually closed (5a58730).
WebSocketServer.prototype.close()was called (772236a).Bug fixes
Sec-WebSocket-Extensionsheader but no extension was requested or if theserver indicates an extension not requested by the client (aca94c8).
Bug fixes
error occurred simultaneously on both peers (b434b9f).
Features
codeproperty describing the specific type of errorthat has occurred (#1901).
Bug fixes
framing error) occurs (8806aa9).
connection is closed due to an error (8806aa9).
Bug fixes
A specially crafted value of the
Sec-Websocket-Protocolheader could be usedto significantly slow down a ws server.
const value = 'b' + ' '.repeat(length) + 'x';
const start = process.hrtime.bigint();
value.trim().split(/ , /);
const end = process.hrtime.bigint();
console.log('length = %d, time = %f ns', length, end - start);
}
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=sizeand/or the
maxHeaderSizeoptions.Commit messages
Package name: ws
Compare
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:

🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs