[Snyk] Security upgrade socket.io from 2.4.0 to 3.0.0

[manuelbcd]

Snyk has created this PR to fix 1 vulnerabilities in the npm dependencies of this project.

Snyk changed the following file(s):

• result/package.json
• result/package-lock.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Regular Expression Denial of Service (ReDoS) npm:debug:20170905	506

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Regular Expression Denial of Service (ReDoS)

[manuelbcd]

Checkmarx One – Scan Summary & Details – 80b80345-ad5d-4556-a455-c4d7304effad

New Issues (1)

Checkmarx found the following issues in this Pull Request

Severity	Issue	Source File / Package	Checkmarx Insight
	CVE-2022-21676	Npm-engine.io-4.0.6	details Recommended version: 6.4.2 Description: Engine.IO is the implementation of transport-based cross-browser/cross-device bi-directional communication layer for Socket.IO. A specially crafted... Attack Vector: NETWORK Attack Complexity: LOW ID: TZBpPBUIyCD1VZjP4Hx4DrmQNyPrtE37ytbESmTM8sI%3D Vulnerable Package

Fixed Issues (8)

Great job! The following issues were fixed in this Pull Request

Severity	Issue	Source File / Package
	CVE-2021-31597	Npm-xmlhttprequest-ssl-1.5.5
	CVE-2022-2421	Npm-socket.io-parser-3.4.1
	CVE-2022-2421	Npm-socket.io-parser-3.3.2
	CVE-2020-28502	Npm-xmlhttprequest-ssl-1.5.5
	CVE-2020-36048	Npm-engine.io-3.5.0
	CVE-2020-28481	Npm-socket.io-2.4.0
	CVE-2021-32640	Npm-ws-7.4.2
	CVE-2024-36751	Npm-parseuri-0.0.6

---

Use @Checkmarx to reach out to us for assistance.

Just send a PR comment with @Checkmarx followed by a natural language request.

Examples: @Checkmarx how are you able to help me? @Checkmarx rescan this PR