[Snyk] Security upgrade libp2p from 0.22.0 to 0.26.1

[adamlaska]

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

Snyk changed the following file(s):

• examples/custom-libp2p/package.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Improper Verification of Cryptographic Signature SNYK-JS-ELLIPTIC-8187303	786
	Server-Side Request Forgery (SSRF) SNYK-JS-IP-7148531	646
	Open Redirect SNYK-JS-NODEFORGE-2330875	586
	Improper Verification of Cryptographic Signature SNYK-JS-NODEFORGE-2430339	579
	Prototype Pollution SNYK-JS-NODEFORGE-2331908	529
	Improper Verification of Cryptographic Signature SNYK-JS-NODEFORGE-2430337	494
	Improper Verification of Cryptographic Signature SNYK-JS-NODEFORGE-2430341	494

---

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:

🦉 Server-Side Request Forgery (SSRF)
🦉 Open Redirect
🦉 Prototype Pollution

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​nodeutils/​defaults-deep@​1.1.0
	libp2p-websocket-star@​0.8.1
	libp2p-mdns@​0.12.3
	libp2p-tcp@​0.12.1
	libp2p-spdy@​0.12.1
	libp2p-railing@​0.9.2
	libp2p-secio@​0.10.1
	libp2p-kad-dht@​0.10.6
	libp2p-mplex@​0.8.5
	libp2p@​0.26.2

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert (click for details)
Warn		[email protected] has a Critical CVE. CVE: GHSA-cvxm-f295-x957 Prototype Pollution in merge-recursive (CRITICAL) Affected versions: <= 0.0.3 Patched version: No patched versions Source: examples/custom-libp2p/package.json ℹ Read more on: This package | This alert | What is a critical CVE? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		[email protected] has a GitHub dependency. Dependency: webcrypto-shim@github:dignifiedquire/webcrypto-shim@#master Location: Package overview Source: examples/custom-libp2p/package.json ℹ Read more on: This package | This alert | What are GitHub dependencies? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Publish the GitHub dependency to npm or a private package repository and consume it from there. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		[email protected] has a GitHub dependency. Dependency: webcrypto-shim@github:dignifiedquire/webcrypto-shim@#master Location: Package overview Source: examples/custom-libp2p/package.json ℹ Read more on: This package | This alert | What are GitHub dependencies? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Publish the GitHub dependency to npm or a private package repository and consume it from there. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		[email protected] has a GitHub dependency. Dependency: webcrypto-shim@github:dignifiedquire/webcrypto-shim@#master Location: Package overview Source: examples/custom-libp2p/package.json ℹ Read more on: This package | This alert | What are GitHub dependencies? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Publish the GitHub dependency to npm or a private package repository and consume it from there. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		[email protected] has a GitHub dependency. Dependency: pull-ws@hugomrdias/pull-ws@#fix/bu Location: Package overview Source: examples/custom-libp2p/package.json ℹ Read more on: This package | This alert | What are GitHub dependencies? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Publish the GitHub dependency to npm or a private package repository and consume it from there. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report