Skip to content
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

[Snyk] Security upgrade sinon from 15.2.0 to 19.0.0 #264

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

adamlaska
Copy link
Owner

snyk-top-banner

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

Snyk changed the following file(s):

  • packages/ipfs-core/package.json

Vulnerabilities that will be fixed with an upgrade:

Issue Score
medium severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-PATHTOREGEXP-7925106
  738  

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)

Copy link

google-cla bot commented Sep 14, 2024

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.

Copy link

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package New capabilities Transitives Size Publisher
npm/ipfs-core-types@0.14.1 Transitive: environment, network +33 3.94 MB npm-service-account-ipfs
npm/ipfs-message-port-protocol@0.15.1 None 0 39 kB npm-service-account-ipfs
npm/it-all@2.0.1 None 0 6.22 kB achingbrain
npm/multiformats@11.0.2 None 0 264 kB npm-service-account-multiformats

🚮 Removed packages: npm/@chainsafe/libp2p-gossipsub@6.3.0, npm/@chainsafe/libp2p-noise@11.0.4, npm/@ipld/car@5.3.2, npm/@ipld/dag-cbor@9.2.1, npm/@ipld/dag-json@10.2.2, npm/@libp2p/bootstrap@6.0.3, npm/@libp2p/crypto@1.0.17, npm/@libp2p/delegated-content-routing@4.0.11, npm/@libp2p/delegated-peer-routing@4.0.14, npm/@libp2p/interface-dht@2.0.3, npm/@libp2p/interface-keys@1.0.8, npm/@libp2p/interface-transport@2.1.3, npm/@libp2p/kad-dht@7.0.3, npm/@libp2p/logger@2.1.1, npm/@libp2p/mplex@7.1.7, npm/@libp2p/peer-id-factory@2.0.4, npm/@libp2p/peer-id@2.0.4, npm/@libp2p/record@3.0.4, npm/@libp2p/websockets@5.0.10, npm/@multiformats/mafmt@11.1.2, npm/@multiformats/multiaddr-to-uri@9.0.8, npm/@multiformats/murmur3@2.1.8, npm/@types/dlv@1.1.4, npm/@types/pako@2.0.3, npm/@types/rimraf@3.0.2, npm/any-signal@3.0.1, npm/array-shuffle@3.0.0, npm/blockstore-core@3.0.0, npm/blockstore-datastore-adapter@5.0.0, npm/browser-readablestream-to-it@2.0.7, npm/dag-jose@4.0.0, npm/datastore-core@8.0.4, npm/datastore-pubsub@7.0.0, npm/delay@5.0.0, npm/dlv@1.1.3

View full report↗︎

Copy link

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert Package NoteSourceCI
Critical CVE npm/gh-pages@4.0.0 ⚠︎

View full report↗︎

Next steps

What is a critical CVE?

Contains a Critical Common Vulnerability and Exposure (CVE).

Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.

Take a deeper look at the dependency

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 support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

  • @SocketSecurity ignore npm/gh-pages@4.0.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants