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 gulp-cli from 2.3.0 to 3.0.0 #7

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

Conversation

kingjay66
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
    • package-lock.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
Yes Proof of Concept
high severity 589/1000
Why? Has a fix available, CVSS 7.5
Prototype Pollution
SNYK-JS-UNSETVALUE-2400660
Yes No Known Exploit

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

Commit messages
Package name: gulp-cli The new version differs by 19 commits.
  • e422eb1 chore: Release 3.0.0 (#248)
  • f495154 chore: Renamed prepublish script to manpage
  • affeda9 feat: Add deprecated warning for gulplog v1 messages (#266)
  • f06ff30 feat: Add versioned handler for gulp v5 (#265)
  • e16d675 feat: Support theming and translations via config files (#260)
  • 9a1d013 chore: Augment `task not found` error with helpful properties (#262)
  • e5c7983 chore!: Only allow js variants for `.gulp` config files (#261)
  • ed86da7 feat!: Upgrade to Liftoff v5 and avoid merging flags/config/env (#259)
  • 36f05d5 fix: Ensure the logger is wired up before running liftoff (#258)
  • 4fc66f6 chore: Revert options & yargs parser changes (#257)
  • c70ce34 chore: Move task list helper functions into the logTasks closure (#256)
  • cb03b9a chore!: Remove support for alpha versions of gulp 4 (#255)
  • f71effa chore: Add a test case for config file in current dir (#253)
  • 0a35a9e chore: Remove custom Windows tmpdir logic in test (#252)
  • 7aeee5d chore!: Remove `--verify` flag (#251)
  • 89a67e5 chore(test): Add test for Windows extended-length paths (#225)
  • 3544dc6 chore!: Normalize repository, dropping node <10.13 support (#239)
  • f0c6730 chore(docs): Updated interpret link to point to gulpjs location (#241)
  • da8241e Docs: Add install section to README (#216)

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)
🦉 Prototype Pollution

Copy link

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

Package New capabilities Transitives Size Publisher
npm/[email protected] environment, filesystem, unsafe Transitive: shell +34 980 kB phated

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
Dynamic require npm/[email protected]
Dynamic require npm/[email protected]
Environment variable access npm/[email protected]
Environment variable access npm/[email protected]
Environment variable access npm/[email protected]
Dynamic require npm/[email protected]
Filesystem access npm/[email protected]
Environment variable access npm/[email protected]
Filesystem access npm/[email protected]
Shell access npm/[email protected]
Environment variable access npm/[email protected]
Dynamic require npm/[email protected]
Filesystem access npm/[email protected]
Filesystem access npm/@netlify/[email protected]
Filesystem access npm/@netlify/[email protected]
Network access npm/@netlify/[email protected]
Environment variable access npm/@netlify/[email protected]
Network access npm/@netlify/[email protected]
Network access npm/@netlify/[email protected]
Dynamic require npm/[email protected]
Dynamic require npm/[email protected]

View full report↗︎

Next steps

What is dynamic require?

Dynamic require can indicate the package is performing dangerous or unsafe dynamic code execution.

Packages should avoid dynamic imports when possible. Audit the use of dynamic require to ensure it is not executing malicious or vulnerable code.

What is environment variable access?

Package accesses environment variables, which may be a sign of credential stuffing or data theft.

Packages should be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to.

What is filesystem access?

Accesses the file system, and could potentially read sensitive data.

If a package must read the file system, clarify what it will read and ensure it reads only what it claims to. If appropriate, packages can leave file system access to consumers and operate on data passed to it instead.

What is shell access?

This module accesses the system shell. Accessing the system shell increases the risk of executing arbitrary code.

Packages should avoid accessing the shell which can reduce portability, and make it easier for malicious shell access to be introduced.

What is network access?

This module accesses the network.

Packages should remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use.

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