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] Fix for 7 vulnerabilities #76

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

Conversation

adamlaska
Copy link
Owner

snyk-top-banner

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

Snyk changed the following file(s):

  • package.json
  • package-lock.json

Vulnerabilities that will be fixed with an upgrade:

Issue Score
critical severity Improper Verification of Cryptographic Signature
SNYK-JS-ELLIPTIC-7577916
  776  
critical severity Improper Verification of Cryptographic Signature
SNYK-JS-ELLIPTIC-7577917
  776  
critical severity Improper Verification of Cryptographic Signature
SNYK-JS-ELLIPTIC-7577918
  776  
high severity Improper Verification of Cryptographic Signature
SNYK-JS-ELLIPTIC-8187303
  756  
high severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-PATHTOREGEXP-8482416
  721  
high severity Improper Verification of Cryptographic Signature
SNYK-JS-ELLIPTIC-8172694
  629  
high severity Improper Verification of Cryptographic Signature
SNYK-JS-BROWSERIFYSIGN-6037026
  589  

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 Dec 6, 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/@ensdomains/[email protected] None 0 2.1 MB makoto_inoue
npm/@ensdomains/[email protected] None 0 59.7 MB makoto_inoue
npm/[email protected] None 0 13.8 kB ljharb
npm/[email protected] None 0 22.9 kB ljharb
npm/[email protected] None 0 30.9 kB ljharb
npm/[email protected] None 0 11.8 kB ljharb
npm/[email protected] None 0 12.3 kB ljharb
npm/[email protected] None 0 845 kB alcuadrado
npm/[email protected] None 0 68.4 kB holgerd77
npm/[email protected] None 0 795 kB evertonfraga
npm/[email protected] None 0 66.2 kB holgerd77
npm/[email protected] None 0 310 kB holgerd77
npm/[email protected] None 0 46.1 kB alenaivanova
npm/[email protected] None 0 162 kB ralxz
npm/[email protected] None 0 10.4 MB ricmoo
npm/[email protected] None 0 460 kB silentcicero
npm/[email protected] None 0 225 kB silentcicero
npm/[email protected] None 0 21.8 kB riaevangelist
npm/[email protected] None 0 40.2 kB rangermauve
npm/[email protected] None 0 37.8 kB lpinca
npm/[email protected] None 0 82.8 kB goto-bus-stop
npm/[email protected] network 0 314 kB rexxars
npm/[email protected] None 0 5.13 kB dcousens
npm/[email protected] filesystem 0 4.31 kB kevva
npm/[email protected] shell 0 23 kB tsertkov
npm/[email protected] environment, shell 0 19.9 kB sindresorhus
npm/[email protected] None 0 3.84 kB sindresorhus
npm/[email protected] filesystem 0 3.79 kB kevva
npm/[email protected] None 0 59.8 kB cowboy
npm/[email protected] None 0 26 kB jonschlinkert

🚮 Removed packages: npm/@ensdomains/[email protected], npm/@ensdomains/[email protected], npm/@nomiclabs/[email protected], npm/@nomiclabs/[email protected], npm/@truffle/[email protected], npm/@truffle/[email protected], npm/@truffle/[email protected], npm/@truffle/[email protected], npm/@truffle/[email protected], npm/@truffle/[email protected], npm/@truffle/[email protected], npm/@truffle/[email protected], npm/@trufflesuite/[email protected], npm/@types/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected]

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
Possible typosquat attack npm/[email protected] ⚠︎

View full report↗︎

Next steps

What is a typosquat?

Package name is similar to other popular packages and may not be the package you want.

Use care when consuming similarly named packages and ensure that you did not intend to consume a different package. Malicious packages often publish using similar names as existing popular packages.

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