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 from 4.0.2 to 5.0.0 #378

Open
wants to merge 1 commit into
base: 1.0.x
Choose a base branch
from

Conversation

riteshgurung
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 `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
⚠️ Warning
Failed to update the package-lock.json, please update manually before merging.

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 696/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 7.5
Denial of Service (DoS)
SNYK-JS-DECODEURICOMPONENT-3149970
Yes 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-GLOBPARENT-1016905
Yes 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
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 The new version differs by 45 commits.
  • 5c4c547 chore: Release 5.0.0 (#2762)
  • bf72116 chore: Add index.mjs to files list
  • b00de68 feat: Provide an ESM export (#2760)
  • 72668c6 chore!: Normalize repository, dropping node <10.13 support (#2758)
  • 85896d4 chore(docs): Update stream handbook link (#2711)
  • 818bd73 Docs: Remove gulp-sourcemaps because it is built-in (#2592)
  • 598f971 Docs: Fix broken link in recipe (#2571)
  • 9877de0 Docs: Guide CustomRegistries to maintain properties on tasks (fixes #2561) (#2565)
  • f91c388 Docs: Remove typo in custom registry docs (#2543)
  • df25250 Docs: Fix typo in task docs (#2524)
  • b6d6d7c Docs: fix recipe link (#2526)
  • c26ebcb Docs: Cleanup registry error message subtitles
  • d51c6eb Docs: Rename the automate releases recipe file
  • 4c1bead Docs: Add subtitles for registry error messages (#2502)
  • 6e56ed8 Docs: Update and refactor release workflow recipe (#2498)
  • 131b702 Docs: Remove recipe for using a config file
  • c5ff7e0 Docs: Remove recipe for splitting tasks in files
  • 147327c Docs: Remove recipe for specifying a CWD
  • 1a653a9 Docs: Remove recipe for running shell commands
  • e1190ea Docs: Remove recipe for exporting tasks
  • c4305df Docs: Remove recipe for running tasks in series
  • 486f927 Docs: Remove recipes for selecting changed files
  • b7b70b8 Docs: Fix some links
  • 93564bd Docs: Add advanced section for creation of custom registries (#2479)

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

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