-
Notifications
You must be signed in to change notification settings - Fork 4
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
Update dependency ws to v6.2.3 [SECURITY] #612
Open
renovate
wants to merge
1
commit into
master
Choose a base branch
from
renovate/npm-ws-vulnerability
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
renovate
bot
force-pushed
the
renovate/npm-ws-vulnerability
branch
from
July 6, 2024 02:35
7beacde
to
e86957c
Compare
renovate
bot
force-pushed
the
renovate/npm-ws-vulnerability
branch
from
August 5, 2024 10:17
e86957c
to
590ee22
Compare
renovate
bot
force-pushed
the
renovate/npm-ws-vulnerability
branch
from
August 22, 2024 00:21
590ee22
to
469d7d9
Compare
renovate
bot
force-pushed
the
renovate/npm-ws-vulnerability
branch
from
August 23, 2024 20:02
469d7d9
to
f78264f
Compare
renovate
bot
force-pushed
the
renovate/npm-ws-vulnerability
branch
from
August 28, 2024 16:17
f78264f
to
2b01a26
Compare
renovate
bot
force-pushed
the
renovate/npm-ws-vulnerability
branch
from
September 4, 2024 09:37
2b01a26
to
a285dd2
Compare
renovate
bot
force-pushed
the
renovate/npm-ws-vulnerability
branch
from
September 11, 2024 12:46
a285dd2
to
a3f5f46
Compare
renovate
bot
force-pushed
the
renovate/npm-ws-vulnerability
branch
from
September 12, 2024 13:18
a3f5f46
to
46e6d81
Compare
renovate
bot
force-pushed
the
renovate/npm-ws-vulnerability
branch
from
September 16, 2024 10:13
46e6d81
to
17c4fe2
Compare
renovate
bot
force-pushed
the
renovate/npm-ws-vulnerability
branch
from
September 24, 2024 13:04
17c4fe2
to
6b440fb
Compare
renovate
bot
force-pushed
the
renovate/npm-ws-vulnerability
branch
from
October 4, 2024 22:59
6b440fb
to
9cacbeb
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
0 participants
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:
6.2.2
->6.2.3
GitHub Vulnerability Alerts
CVE-2024-37890
Impact
A request with a number of headers exceeding the
server.maxHeadersCount
threshold could be used to crash a ws server.Proof of concept
Patches
The vulnerability was fixed in [email protected] (websockets/ws@e55e510) and backported to [email protected] (websockets/ws@22c2876), [email protected] (websockets/ws@eeb76d3), and [email protected] (websockets/ws@4abd8f6)
Workarounds
In vulnerable versions of ws, the issue can be mitigated in the following ways:
--max-http-header-size=size
and/or themaxHeaderSize
options so that no more headers than theserver.maxHeadersCount
limit can be sent.server.maxHeadersCount
to0
so that no limit is applied.Credits
The vulnerability was reported by Ryan LaPointe in https://github.com/websockets/ws/issues/2230.
References
Release Notes
websockets/ws (ws)
v6.2.3
Compare Source
Bug fixes
e55e510
to the 6.x release line (eeb76d3
).Configuration
📅 Schedule: Branch creation - "" in timezone Europe/London, Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, 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.