-
Notifications
You must be signed in to change notification settings - Fork 0
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
fix(deps): update dependency socket.io to v2 [security] #6
Open
renovate
wants to merge
1
commit into
master
Choose a base branch
from
renovate/npm-socket.io-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-socket.io-vulnerability
branch
from
October 25, 2021 22:04
3719344
to
0662583
Compare
renovate
bot
changed the title
Pin dependency socket.io to v0.9.19 [SECURITY]
Update dependency socket.io to v2 [SECURITY]
Oct 25, 2021
renovate
bot
force-pushed
the
renovate/npm-socket.io-vulnerability
branch
from
October 25, 2021 22:09
0662583
to
2fa03a8
Compare
renovate
bot
changed the title
Update dependency socket.io to v2 [SECURITY]
Update dependency socket.io to v4 [SECURITY]
Oct 25, 2021
renovate
bot
force-pushed
the
renovate/npm-socket.io-vulnerability
branch
from
October 25, 2021 22:13
2fa03a8
to
c57c6c2
Compare
renovate
bot
changed the title
Update dependency socket.io to v4 [SECURITY]
Update dependency socket.io to ~0.9.19 [SECURITY]
Oct 25, 2021
renovate
bot
force-pushed
the
renovate/npm-socket.io-vulnerability
branch
from
October 26, 2021 00:49
c57c6c2
to
149ad59
Compare
renovate
bot
changed the title
Update dependency socket.io to ~0.9.19 [SECURITY]
Update dependency socket.io to v2 [SECURITY]
Oct 26, 2021
renovate
bot
force-pushed
the
renovate/npm-socket.io-vulnerability
branch
from
October 28, 2021 15:33
149ad59
to
19740df
Compare
renovate
bot
changed the title
Update dependency socket.io to v2 [SECURITY]
Update dependency socket.io to ~0.9.19 [SECURITY]
Oct 28, 2021
renovate
bot
force-pushed
the
renovate/npm-socket.io-vulnerability
branch
from
October 28, 2021 17:22
19740df
to
07003d0
Compare
renovate
bot
changed the title
Update dependency socket.io to ~0.9.19 [SECURITY]
Update dependency socket.io to v2 [SECURITY]
Oct 28, 2021
renovate
bot
force-pushed
the
renovate/npm-socket.io-vulnerability
branch
from
October 29, 2021 03:51
07003d0
to
6ccf6b9
Compare
renovate
bot
changed the title
Update dependency socket.io to v2 [SECURITY]
Update dependency socket.io to ~0.9.19 [SECURITY]
Oct 29, 2021
renovate
bot
force-pushed
the
renovate/npm-socket.io-vulnerability
branch
from
October 29, 2021 05:49
6ccf6b9
to
ddd7880
Compare
renovate
bot
changed the title
Update dependency socket.io to ~0.9.19 [SECURITY]
Update dependency socket.io to v2 [SECURITY]
Oct 29, 2021
renovate
bot
force-pushed
the
renovate/npm-socket.io-vulnerability
branch
from
November 4, 2021 12:01
ddd7880
to
0c80785
Compare
renovate
bot
changed the title
Update dependency socket.io to v2 [SECURITY]
Update dependency socket.io to ~0.9.19 [SECURITY]
Nov 4, 2021
renovate
bot
force-pushed
the
renovate/npm-socket.io-vulnerability
branch
from
November 4, 2021 13:19
0c80785
to
b36d42e
Compare
renovate
bot
changed the title
Update dependency socket.io to ~0.9.19 [SECURITY]
Update dependency socket.io to v2 [SECURITY]
Nov 4, 2021
renovate
bot
force-pushed
the
renovate/npm-socket.io-vulnerability
branch
from
November 4, 2021 17:12
b36d42e
to
92972d5
Compare
renovate
bot
changed the title
Update dependency socket.io to v2 [SECURITY]
Update dependency socket.io to ~0.9.19 [SECURITY]
Nov 4, 2021
renovate
bot
force-pushed
the
renovate/npm-socket.io-vulnerability
branch
from
November 4, 2021 19:45
92972d5
to
326b4e2
Compare
renovate
bot
changed the title
Update dependency socket.io to ~0.9.19 [SECURITY]
Update dependency socket.io to v2 [SECURITY]
Nov 4, 2021
renovate
bot
changed the title
Update dependency socket.io to v2 [SECURITY]
Update dependency socket.io to ~0.9.19 [SECURITY]
Nov 5, 2021
renovate
bot
force-pushed
the
renovate/npm-socket.io-vulnerability
branch
2 times, most recently
from
November 5, 2021 14:35
374255d
to
1c79c6e
Compare
renovate
bot
changed the title
Update dependency socket.io to ~0.9.19 [SECURITY]
Update dependency socket.io to v2 [SECURITY]
Nov 5, 2021
renovate
bot
force-pushed
the
renovate/npm-socket.io-vulnerability
branch
from
November 8, 2021 13:17
1c79c6e
to
9eb1217
Compare
renovate
bot
changed the title
Update dependency socket.io to v2 [SECURITY]
Update dependency socket.io to ~0.9.19 [SECURITY]
Nov 8, 2021
renovate
bot
force-pushed
the
renovate/npm-socket.io-vulnerability
branch
from
June 6, 2024 02:51
544dcc0
to
1536bd6
Compare
renovate
bot
changed the title
fix(deps): update dependency socket.io to v2 [security]
fix(deps): update dependency socket.io to v4 [security]
Jun 6, 2024
renovate
bot
force-pushed
the
renovate/npm-socket.io-vulnerability
branch
from
June 7, 2024 04:43
1536bd6
to
dcf26dc
Compare
renovate
bot
changed the title
fix(deps): update dependency socket.io to v4 [security]
fix(deps): update dependency socket.io to v2 [security]
Jun 7, 2024
renovate
bot
force-pushed
the
renovate/npm-socket.io-vulnerability
branch
from
June 19, 2024 23:42
dcf26dc
to
b78dbbd
Compare
renovate
bot
force-pushed
the
renovate/npm-socket.io-vulnerability
branch
from
June 28, 2024 02:20
b78dbbd
to
c3b84c9
Compare
renovate
bot
changed the title
fix(deps): update dependency socket.io to v2 [security]
fix(deps): update dependency socket.io to v4 [security]
Jun 28, 2024
renovate
bot
force-pushed
the
renovate/npm-socket.io-vulnerability
branch
from
June 29, 2024 08:21
c3b84c9
to
21f6fca
Compare
renovate
bot
changed the title
fix(deps): update dependency socket.io to v4 [security]
fix(deps): update dependency socket.io to v2 [security]
Jun 29, 2024
renovate
bot
force-pushed
the
renovate/npm-socket.io-vulnerability
branch
from
July 14, 2024 23:24
21f6fca
to
74c3a7f
Compare
renovate
bot
changed the title
fix(deps): update dependency socket.io to v2 [security]
fix(deps): update dependency socket.io to v4 [security]
Jul 14, 2024
renovate
bot
force-pushed
the
renovate/npm-socket.io-vulnerability
branch
from
July 15, 2024 05:36
74c3a7f
to
365e191
Compare
renovate
bot
changed the title
fix(deps): update dependency socket.io to v4 [security]
fix(deps): update dependency socket.io to v2 [security]
Jul 15, 2024
renovate
bot
force-pushed
the
renovate/npm-socket.io-vulnerability
branch
from
July 21, 2024 17:58
365e191
to
b7c1570
Compare
renovate
bot
changed the title
fix(deps): update dependency socket.io to v2 [security]
fix(deps): update dependency socket.io to v4 [security]
Jul 21, 2024
renovate
bot
force-pushed
the
renovate/npm-socket.io-vulnerability
branch
from
July 24, 2024 02:43
b7c1570
to
dbe070b
Compare
renovate
bot
changed the title
fix(deps): update dependency socket.io to v4 [security]
fix(deps): update dependency socket.io to v2 [security]
Jul 24, 2024
renovate
bot
force-pushed
the
renovate/npm-socket.io-vulnerability
branch
from
July 29, 2024 11:39
dbe070b
to
6941add
Compare
renovate
bot
changed the title
fix(deps): update dependency socket.io to v2 [security]
fix(deps): update dependency socket.io to v4 [security]
Jul 29, 2024
renovate
bot
force-pushed
the
renovate/npm-socket.io-vulnerability
branch
from
July 31, 2024 08:52
6941add
to
182c0e4
Compare
renovate
bot
changed the title
fix(deps): update dependency socket.io to v4 [security]
fix(deps): update dependency socket.io to v2 [security]
Jul 31, 2024
renovate
bot
force-pushed
the
renovate/npm-socket.io-vulnerability
branch
from
October 10, 2024 17:54
182c0e4
to
d1e8bb5
Compare
renovate
bot
changed the title
fix(deps): update dependency socket.io to v2 [security]
fix(deps): update dependency socket.io to v4 [security]
Oct 10, 2024
renovate
bot
force-pushed
the
renovate/npm-socket.io-vulnerability
branch
from
October 11, 2024 05:57
d1e8bb5
to
bbab1dd
Compare
renovate
bot
changed the title
fix(deps): update dependency socket.io to v4 [security]
fix(deps): update dependency socket.io to v2 [security]
Oct 11, 2024
renovate
bot
force-pushed
the
renovate/npm-socket.io-vulnerability
branch
from
October 30, 2024 02:52
bbab1dd
to
55cfdac
Compare
renovate
bot
changed the title
fix(deps): update dependency socket.io to v2 [security]
fix(deps): update dependency socket.io to v4 [security]
Oct 30, 2024
renovate
bot
force-pushed
the
renovate/npm-socket.io-vulnerability
branch
from
November 1, 2024 05:45
55cfdac
to
652a5c3
Compare
renovate
bot
changed the title
fix(deps): update dependency socket.io to v4 [security]
fix(deps): update dependency socket.io to v2 [security]
Nov 1, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
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:
~0.9.13
->~2.5.1
GitHub Vulnerability Alerts
CVE-2020-28481
The package socket.io before 2.4.0 are vulnerable to Insecure Defaults due to CORS Misconfiguration. All domains are whitelisted by default.
CVE-2024-38355
Impact
A specially crafted Socket.IO packet can trigger an uncaught exception on the Socket.IO server, thus killing the Node.js process.
Affected versions
4.6.2...latest
3.0.0...4.6.1
socket.io@4.6.2
(at least)2.3.0...2.5.0
socket.io@2.5.1
Patches
This issue is fixed by socketio/socket.io@15af22f, included in
socket.io@4.6.2
(released in May 2023).The fix was backported in the 2.x branch today: socketio/socket.io@d30630b
Workarounds
As a workaround for the affected versions of the
socket.io
package, you can attach a listener for the "error" event:For more information
If you have any questions or comments about this advisory:
Thanks a lot to Paul Taylor for the responsible disclosure.
References
Release Notes
socketio/socket.io (socket.io)
v2.5.1
Compare Source
Bug Fixes
Links:
-
~3.6.0
(no change)~7.5.10
v2.5.0
Compare Source
The default value of the
maxHttpBufferSize
option has been decreased from 100 MB to 1 MB, in order to prevent attacks by denial of service.Security advisory: GHSA-j4f2-536g-r55m
Bug Fixes
Links:
~3.6.0
(diff)~7.4.2
v2.4.1
Compare Source
Reverts
v2.4.0
Compare Source
Related blog post: https://socket.io/blog/socket-io-2-4-0/
Features (from Engine.IO)
Bug Fixes
Previously, CORS was enabled by default, which meant that a Socket.IO server sent the necessary CORS headers (
Access-Control-Allow-xxx
) to any domain. This will not be the case anymore, and you now have to explicitly enable it.Please note that you are not impacted if:
origins
option to restrict the list of allowed domainsThis commit also removes the support for '*' matchers and protocol-less URL:
To restore the previous behavior (please use with caution):
See also:
Thanks a lot to @ni8walk3r for the security report.
Links:
~3.5.0
~7.4.2
v2.3.0
Compare Source
This release mainly contains a bump of the
engine.io
andws
packages, but no additional features.Links:
~3.4.0
(diff: socketio/engine.io@3.3.1...3.4.2)^7.1.2
(diff: websockets/ws@6.1.2...7.3.1)v2.2.0
Compare Source
Features
Bug fixes
Links
~3.3.1
(diff: socketio/engine.io@3.2.0...3.3.1)~6.1.0
(diff: websockets/ws@3.3.1...6.1.2)v2.1.1
Compare Source
Features
Bug fixes
(client) fire an error event on middleware failure for non-root namespace (https://github.com/socketio/socket.io-client/pull/1202)
Links:
~3.2.0
~3.3.1
v2.1.0
Compare Source
Features
Bug fixes
Important note⚠️ from Engine.IO 3.2.0 release
There are two non-breaking changes that are somehow quite important:
ws
was reverted as the default wsEngine (https://github.com/socketio/engine.io/pull/550), as there was several blocking issues withuws
. You can still useuws
by runningnpm install uws --save
in your project and using thewsEngine
option:pingTimeout
now defaults to 5 seconds (instead of 60 seconds): https://github.com/socketio/engine.io/pull/551Links:
~3.2.0
(diff: socketio/engine.io@3.1.0...3.2.0)~3.3.1
(diff: websockets/ws@2.3.1...3.3.1)v2.0.4
Compare Source
Bug fixes
Links:
engine.io
: -ws
: -v2.0.3
Compare Source
Bug fixes
Links:
engine.io
: -ws
: -v2.0.2
Compare Source
Bug fixes
Links:
engine.io
: -ws
: -v2.0.1
Compare Source
Bug fixes
- update path of client file (#2934)
Links:
engine.io
: -ws
: -v2.0.0
Compare Source
This major release brings several performance improvements:
uws is now the default Websocket engine. It should bring significant improvement in performance (particularly in terms of memory consumption) (https://github.com/socketio/engine.io/releases/tag/2.0.0)
the Engine.IO and Socket.IO handshake packets were merged, reducing the number of roundtrips necessary to establish a connection. (#2833)
it is now possible to provide a custom parser according to the needs of your application (#2829). Please take a look at the example for more information.
Please note that this release is not backward-compatible, due to:
Please also note that if you are using a self-signed certificate,
rejectUnauthorized
now defaults totrue
(https://github.com/socketio/engine.io-client/pull/558).Finally, the API documentation is now in the repository (here), and the content of the website here. Do not hesitate if you see something wrong or missing!
The full list of changes:
local
flag (#2816)clients
method in the API documentation (#2812)Besides, we are proud to announce that Socket.IO is now a part of open collective: https://opencollective.com/socketio. More on that later.
v1.7.4
Compare Source
v1.7.3
Compare Source
v1.7.2
Compare Source
v1.7.1
Compare Source
(following
socket.io-client
update)v1.7.0
Compare Source
local
flag (#2628)v1.6.0
Compare Source
v1.5.1
Compare Source
client
in test script (#2731)v1.5.0
Compare Source
v1.4.8
Compare Source
v1.4.7
Compare Source
v1.4.6
Compare Source
v1.4.5
Compare Source
v1.4.4
Compare Source
v1.4.3
Compare Source
v1.4.2
Compare Source
v1.4.1
Compare Source
v1.4.0
Compare Source
v1.3.7
Compare Source
v1.3.6
Compare Source
v1.3.5
Compare Source
v1.3.4
Compare Source
v1.3.3
Compare Source
v1.3.2
Compare Source
v1.3.1
Compare Source
v1.3.0
Compare Source
v1.2.1
Compare Source
v1.2.0
Compare Source
v1.1.0
Compare Source
v1.0.6
Compare Source
v1.0.5
Compare Source
v1.0.4
Compare Source
v1.0.3
Compare Source
v1.0.2
Compare Source
v1.0.1
Compare Source
v1.0.0
Compare Source
v0.9.19
Compare Source
v0.9.18
Compare Source
v0.9.15
Compare Source
v0.9.14
Compare Source
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 this update again.
This PR was generated by Mend Renovate. View the repository job log.