Skip to content

[Snyk] Fix for 16 vulnerabilities #230

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

Open
wants to merge 1 commit into
base: CircleCI-v2
Choose a base branch
from

Conversation

adamlaska
Copy link
Owner

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


Snyk has created this PR to fix one or more vulnerable packages in the `npm` dependencies of this project.

Changes included in this PR

  • Changes to the following files to upgrade the vulnerable dependencies to a fixed version:
    • package.json

Vulnerabilities that will be fixed

With an upgrade:
Severity Priority Score (*) Issue Breaking Change Exploit Maturity
high severity 696/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 7.5
Regular Expression Denial of Service (ReDoS)
SNYK-JS-ANSIREGEX-1583908
No Proof of Concept
medium severity 554/1000
Why? Has a fix available, CVSS 6.8
Cryptographic Issues
SNYK-JS-ELLIPTIC-1064899
No No Known Exploit
medium severity 509/1000
Why? Has a fix available, CVSS 5.9
Timing Attack
SNYK-JS-ELLIPTIC-511941
No No Known Exploit
high severity 706/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 7.7
Cryptographic Issues
SNYK-JS-ELLIPTIC-571484
No Proof of Concept
medium severity 631/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 6.2
Missing Release of Resource after Effective Lifetime
SNYK-JS-INFLIGHT-6095116
No Proof of Concept
medium severity 586/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 5.3
Regular Expression Denial of Service (ReDoS)
SNYK-JS-LODASH-1018905
No Proof of Concept
high severity 681/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 7.2
Command Injection
SNYK-JS-LODASH-1040724
No Proof of Concept
high severity 686/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 7.3
Prototype Pollution
SNYK-JS-LODASH-450202
No Proof of Concept
high severity 686/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 7.3
Prototype Pollution
SNYK-JS-LODASH-608086
No Proof of Concept
high severity 686/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 7.3
Prototype Pollution
SNYK-JS-LODASH-73638
No Proof of Concept
medium severity 541/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 4.4
Regular Expression Denial of Service (ReDoS)
SNYK-JS-LODASH-73639
No Proof of Concept
high severity 686/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 7.3
Prototype Pollution
SNYK-JS-LODASHSET-1320032
No Proof of Concept
high severity 686/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 7.3
Prototype Pollution
SNYK-JS-NODEFORGE-598677
Yes Proof of Concept
high severity 696/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 7.5
Regular Expression Denial of Service (ReDoS)
SNYK-JS-SEMVER-3247795
No Proof of Concept
medium severity 636/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 6.3
Prototype Pollution
npm:lodash:20180130
No Proof of Concept
high severity 686/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 7.3
Prototype Pollution
npm:merge-recursive:20180415
No Proof of Concept

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

Commit messages
Package name: ipfs-api The new version differs by 30 commits.
  • ead3599 chore: release version v26.1.2
  • b97c833 chore: update contributors
  • 3d3d323 chore: release version v26.1.1
  • fe4a1e7 chore: update contributors
  • e3e4d6c feat: go-ipfs 0.4.18
  • 62b844f feat: upload example works with big files
  • 0175406 chore: release version v26.1.0
  • 9ae5189 chore: update contributors
  • 80725f2 fix: make ping not mix errors with responses (#883)
  • f382ac0 chore: release version v26.0.3
  • 2856afe chore: update contributors
  • 7fb2cff chore: release version v26.0.2
  • 75e0771 chore: update contributors
  • ddf8bee chore: release version v26.0.1
  • a8f37d6 chore: update contributors
  • 0b46750 fix: pin.ls ignored opts when hash was present (#875)
  • 9eaaea3 chore: release version v26.0.0
  • 3f927a9 chore: update contributors
  • 979d8b5 fix: add missing and remove unused dependencies (#879)
  • 0652ac0 chore: update to ipld-dag-cbor 0.13
  • c534375 chore: remove ipld formats re-export (#872)
  • ef49e95 feat: ipns over pubsub (#846)
  • 14a4471 chore: release version v25.0.0
  • 07d6351 chore: update contributors

See the full diff

Package name: ipld The new version differs by 182 commits.

See the full diff

Package name: libp2p-circuit The new version differs by 31 commits.

See the full diff

Package name: libp2p-websocket-star The new version differs by 20 commits.

See the full diff

Package name: peer-book The new version differs by 17 commits.

See the full diff

Check the changes in this PR to ensure they won't cause issues with your project.


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

🛠 Adjust project settings

📚 Read more about Snyk's upgrade and patch logic


Learn how to fix vulnerabilities with free interactive lessons:

🦉 Regular Expression Denial of Service (ReDoS)
🦉 Cryptographic Issues
🦉 Command Injection
🦉 More lessons are available in Snyk Learn

Copy link

google-cla bot commented Feb 2, 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

socket-security bot commented Feb 2, 2024

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

Package New capabilities Transitives Size Publisher
npm/[email protected] filesystem, network Transitive: environment, eval, unsafe +162 67.2 MB daviddias
npm/[email protected] Transitive: filesystem, network, shell +54 22.5 MB achingbrain
npm/[email protected] Transitive: environment, filesystem +75 17.9 MB jacobheun
npm/[email protected] Transitive: environment, filesystem, network, shell +94 19.9 MB jacobheun
npm/[email protected] Transitive: environment, filesystem +63 17 MB vascosantos

🚮 Removed packages: npm/[email protected]

View full report↗︎

Copy link

socket-security bot commented Feb 2, 2024

🚨 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 NoteSource
Install scripts npm/[email protected]
  • Install script: postinstall
  • Source: node scripts/postinstall

View full report↗︎

Next steps

What is an install script?

Install scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts.

Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead.

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/[email protected] or ignore all packages with @SocketSecurity ignore-all

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