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 1 vulnerabilities #18

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

Conversation

Nguyendinhtuan17
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:
    • lp_ui/package.json
    • lp_ui/package-lock.json

Vulnerabilities that will be fixed

With an upgrade:
Severity Priority Score (*) Issue Breaking Change Exploit Maturity
high severity 661/1000
Why? Recently disclosed, Has a fix available, CVSS 7.5
Improper Restriction of Operations within the Bounds of a Memory Buffer
SNYK-JS-SOLANAWEB3JS-6647564
No No Known Exploit

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

Commit messages
Package name: @solana/wallet-adapter-wallets The new version differs by 155 commits.

See the full diff

Package name: @solana/web3.js The new version differs by 75 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:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

Copy link

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

Package New capabilities Transitives Size Publisher
npm/@certusone/[email protected] network Transitive: environment, filesystem +84 159 MB kev1n-peters
npm/@certusone/[email protected] None 0 877 kB evan-gray
npm/@grpc/[email protected] environment, filesystem, network +21 5.62 MB murgatroid99
npm/@improbable-eng/[email protected] network 0 12.1 kB marcuslongmuir
npm/@mysten/[email protected] network +12 5.83 MB ebmifa
npm/@solana/[email protected] network Transitive: environment, filesystem, shell +56 22.9 MB mvines
npm/@solana/[email protected] network +8 11 MB _chido
npm/@types/[email protected] Transitive: environment, eval +18 522 kB types
npm/@types/[email protected] None 0 71.4 kB types
npm/@types/[email protected] None 0 1.66 MB types
npm/@types/[email protected] None 0 1.67 MB types
npm/[email protected] environment, network 0 389 kB jasonsaayman
npm/[email protected] network Transitive: environment, eval, filesystem +5 170 kB dougwilson
npm/[email protected] None 0 20 kB dougwilson
npm/[email protected] eval, filesystem, unsafe 0 309 kB jdalton
npm/[email protected] Transitive: environment, filesystem, network +49 18.2 MB ricmoo
npm/[email protected] Transitive: environment, eval, filesystem, network, shell, unsafe +327 25.2 MB simenb
npm/[email protected] environment, eval, filesystem, unsafe 0 21 MB sosukesuzuki
npm/[email protected] environment, filesystem Transitive: eval, network, shell, unsafe +154 10.4 MB kul
npm/[email protected] None 0 13.5 kB alexjoverm
npm/[email protected] filesystem Transitive: environment, eval, shell +39 4.02 MB palantir
npm/[email protected] None 0 64 MB typescript-bot

🚮 Removed packages: npm/@certusone/[email protected], npm/@craco/[email protected], npm/@material-ui/[email protected], npm/@material-ui/[email protected], npm/@material-ui/[email protected], npm/@metamask/[email protected], npm/@solana/[email protected], npm/@solana/[email protected], npm/@solana/[email protected], npm/@solana/[email protected], npm/@solana/[email protected], npm/@solana/[email protected], npm/@solana/[email protected], npm/@solana/[email protected], npm/@types/[email protected], npm/@types/[email protected], npm/@types/[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 NoteSource
Install scripts npm/[email protected]
  • Install script: install
  • Source: npm run build || echo "secp256k1 bindings compilation fail. Pure JS implementation will be used."
Install scripts npm/[email protected]
  • Install script: install
  • Source: npm run rebuild || echo "Secp256k1 bindings compilation fail. Pure JS implementation will be used."
Install scripts npm/@injectivelabs/[email protected]
  • Install script: postinstall
  • Source: link-module-alias
Install scripts npm/@injectivelabs/[email protected]
  • Install script: postinstall
  • Source: link-module-alias
Install scripts npm/@injectivelabs/[email protected]
  • Install script: postinstall
  • Source: link-module-alias
Install scripts npm/@injectivelabs/[email protected]
  • Install script: postinstall
  • Source: link-module-alias
Install scripts npm/@injectivelabs/[email protected]
  • Install script: postinstall
  • Source: link-module-alias
Install scripts npm/@injectivelabs/[email protected]
  • Install script: postinstall
  • Source: link-module-alias
Install scripts npm/@injectivelabs/[email protected]
  • Install script: postinstall
  • Source: link-module-alias
Install scripts npm/@injectivelabs/[email protected]
  • Install script: postinstall
  • Source: link-module-alias
Install scripts npm/@injectivelabs/[email protected]
  • Install script: postinstall
  • Source: link-module-alias

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
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants