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 sao from 0.22.17 to 1.0.0 #461

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

Conversation

titanism
Copy link
Contributor

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 `yarn` 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
    • yarn.lock

Note for zero-installs users

If you are using the Yarn feature zero-installs that was introduced in Yarn V2, note that this PR does not update the .yarn/cache/ directory meaning this code cannot be pulled and immediately developed on as one would expect for a zero-install project - you will need to run yarn to update the contents of the ./yarn/cache directory.
If you are not using zero-install you can ignore this as your flow should likely be unchanged.

Vulnerabilities that will be fixed

With an upgrade:
Severity Priority Score (*) Issue Breaking Change Exploit Maturity
medium severity 551/1000
Why? Recently disclosed, Has a fix available, CVSS 5.3
Improper Control of Dynamically-Managed Code Resources
SNYK-JS-EJS-6689533
Yes No Known Exploit

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

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:

🦉 Improper Control of Dynamically-Managed Code Resources

Copy link

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

Package New capabilities Transitives Size Publisher
npm/[email protected] environment, filesystem 0 48 kB substack
npm/[email protected] None 0 755 kB aexmachina
npm/[email protected] None 0 39.7 kB matteo.collina
npm/[email protected] filesystem 0 9.88 kB henrikjoreteg
npm/[email protected] filesystem 0 151 kB titanism
npm/[email protected] None 0 395 kB wooorm
npm/[email protected] network 0 8.74 kB sindresorhus
npm/[email protected] None 0 20 kB sindresorhus
npm/[email protected] filesystem 0 21.8 kB sindresorhus
npm/[email protected] unsafe 0 8.91 kB loganfsmyth
npm/[email protected] environment, filesystem, network, unsafe 0 60.9 kB phated
npm/[email protected] None 0 6.63 kB contra
npm/[email protected] None 0 45 kB robrich
npm/[email protected] None +1 41.5 kB sindresorhus
npm/[email protected] None 0 23.6 kB vohof
npm/[email protected] None 0 14.3 kB unsoundscapes
npm/[email protected] None 0 755 kB ilyakam
npm/[email protected] None 0 20.9 kB phated
npm/[email protected] filesystem 0 16 kB sindresorhus
npm/[email protected] None 0 1.71 MB highlightjs_bot
npm/[email protected] None 0 122 kB devote
npm/[email protected] None 0 3.8 kB sindresorhus
npm/[email protected] None 0 35.7 kB indutny
npm/[email protected] None 0 13.5 kB niftylettuce
npm/[email protected] None 0 56.7 kB omrilotan
npm/[email protected] None 0 146 kB eisbehr
npm/[email protected] None 0 16.1 kB feross
npm/[email protected] None 0 33.5 kB screeny05
npm/[email protected] None 0 1.32 MB timmywil
npm/[email protected] None 0 17.1 kB niftylettuce
npm/[email protected] None 0 156 kB niftylettuce
npm/[email protected] None 0 1.41 MB bnjmnt4n
npm/[email protected] environment, filesystem 0 18.9 kB niftylettuce
npm/[email protected] environment 0 12.7 kB shaunwarman
npm/[email protected] None 0 201 kB vitaly
npm/[email protected] None 0 17.6 kB flet
npm/[email protected] None 0 7.28 kB valeriangalliat
npm/[email protected] None 0 76.9 kB linsir
npm/[email protected] None 0 553 kB vitaly
npm/[email protected] None 0 3.88 kB nodkz
npm/[email protected] None 0 18.7 kB niftylettuce
npm/[email protected] None 0 8.18 kB nkzawa
npm/[email protected] None 0 11.6 kB niftylettuce
npm/[email protected] None 0 70.4 kB viveleroi
npm/[email protected] network +1 1.97 MB vkarpov15
npm/[email protected] environment, filesystem 0 648 kB niftylettuce
npm/[email protected] environment, filesystem, network, shell 0 481 kB andris
npm/[email protected] None 0 336 kB adamwdraper
npm/[email protected] None 0 25.6 kB geraldyeo
npm/[email protected] None 0 8.69 kB sindresorhus
npm/[email protected] None 0 5.17 kB sindresorhus
npm/[email protected] None 0 21.7 kB niftylettuce
npm/[email protected] None 0 42.8 kB saintedlama
npm/[email protected] None +1 205 kB ejhayes
npm/[email protected] None 0 337 kB matteo.collina
npm/[email protected] None 0 17.7 kB blakeembrey
npm/[email protected] None 0 1.72 MB fezvrasta
npm/[email protected] None 0 10.1 kB niftylettuce
npm/[email protected] environment, eval, filesystem 0 59.7 kB pug-bot
npm/[email protected] filesystem 0 182 kB soldair
npm/[email protected] None 0 216 kB ljharb
npm/[email protected] None 0 21.6 kB niftylettuce
npm/[email protected] None 0 3.32 kB sindresorhus
npm/[email protected] None 0 75.6 kB boutell
npm/[email protected] None 0 37.2 kB klaussinani
npm/[email protected] None 0 167 kB pid
npm/[email protected] None 0 1.46 MB eriwen
npm/[email protected] None 0 17.9 kB ericnorris
npm/[email protected] environment, filesystem, network 0 744 kB niftylettuce
npm/[email protected] None 0 562 kB limonte
npm/[email protected] None 0 3.19 kB sindresorhus
npm/[email protected] None 0 30.7 kB al88
npm/[email protected] None 0 646 kB profnandaa
npm/[email protected] None 0 3.46 MB wheels

🚮 Removed packages: npm/@babel/[email protected], npm/@babel/[email protected], npm/@babel/[email protected], npm/@babel/[email protected], npm/@babel/[email protected], npm/@babel/[email protected], npm/@babel/[email protected], npm/@babel/[email protected], npm/@babel/[email protected], npm/@babel/[email protected], npm/@babel/[email protected], npm/@babel/[email protected], npm/@babel/[email protected], npm/@babel/[email protected], npm/@babel/[email protected], npm/@babel/[email protected], npm/@grpc/[email protected], npm/@jridgewell/[email protected], npm/@nodelib/[email protected], npm/@protobufjs/[email protected], npm/@sinonjs/[email protected], npm/@tootallnate/[email protected], npm/@types/[email protected], npm/@types/[email protected], npm/@types/[email protected], npm/@types/[email protected], npm/@types/[email protected], npm/@types/[email protected], npm/@types/[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], 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], 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], 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], 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], 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 NoteSource
Install scripts npm/[email protected]
  • Install script: postinstall
  • Source: node scripts/postinstall || echo "ignore"
Install scripts npm/[email protected]
  • Install script: postinstall
  • Source: node ./postinstall.js

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