Skip to content

[Snyk] Upgrade socket.io from 2.2.0 to 2.5.0#1

Open
ZukAd14 wants to merge 1 commit intomasterfrom
snyk-upgrade-511fc3bbc09cb35431ccfb4a1a8cc0da
Open

[Snyk] Upgrade socket.io from 2.2.0 to 2.5.0#1
ZukAd14 wants to merge 1 commit intomasterfrom
snyk-upgrade-511fc3bbc09cb35431ccfb4a1a8cc0da

Conversation

@ZukAd14
Copy link
Owner

@ZukAd14 ZukAd14 commented Aug 3, 2023

This PR was automatically created by Snyk using the credentials of a real user.


Snyk has created this PR to upgrade socket.io from 2.2.0 to 2.5.0.

ℹ️ 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.


  • The recommended version is 4 versions ahead of your current version.
  • The recommended version was released a year ago, on 2022-06-26.

The recommended version fixes:

Severity Issue PriorityScore (*) Exploit Maturity
Denial of Service (DoS)
SNYK-JS-ENGINEIO-3136336
589/1000
Why? Has a fix available, CVSS 7.5
No Known Exploit
Insecure Defaults
SNYK-JS-SOCKETIO-1024859
589/1000
Why? Has a fix available, CVSS 7.5
Proof of Concept
Regular Expression Denial of Service (ReDoS)
SNYK-JS-WS-1296835
589/1000
Why? Has a fix available, CVSS 7.5
Proof of Concept

(*) Note that the real score may have changed since the PR was raised.


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

Snyk has created this PR to upgrade socket.io from 2.2.0 to 2.5.0.

See this package in npm:


See this project in Snyk:
https://app.snyk.io/org/zukad14/project/a5331f32-1be3-4db1-a4bb-3286292fa730?utm_source=github&utm_medium=referral&page=upgrade-pr
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants