-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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.
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
chore(deps): update dependency ws to v5.2.3 [security] #16733
Conversation
See the guidelines for reviewing dependency updates for info on how to review dependency update PRs. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
devDependency
Test summaryRun details
View run in Cypress Dashboard ➡️ This comment has been generated by cypress-bot as a result of this project's GitHub integration settings. You can manage this integration in this project's settings in the Cypress Dashboard |
5d42032
to
4cf6c72
Compare
4cf6c72
to
e4a9d92
Compare
65a4964
to
fbe70b0
Compare
f2c1257
to
5843dcb
Compare
5843dcb
to
56310fb
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great, backport fix so we don't have to upgrade to 7.0. Although this is not a vulnerability we need to worry about, going to approve to close this PR.
56310fb
to
f57071e
Compare
) Co-authored-by: Renovate Bot <[email protected]>
This PR contains the following updates:
5.2.2
->5.2.3
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
v5.2.3
Compare Source
Bug fixes
00c425e
to the 5.x release line (76d47c1
).Configuration
📅 Schedule: "" in timezone America/New_York.
🚦 Automerge: Enabled.
♻ 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 has been generated by WhiteSource Renovate. View repository job log here.