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] Upgrade grunt-cli from 1.3.2 to 1.4.3 #28

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

Conversation

snyk-bot
Copy link

Snyk has created this PR to upgrade grunt-cli from 1.3.2 to 1.4.3.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 4 versions ahead of your current version.
  • The recommended version was released 2 years ago, on 2021-05-25.

The recommended version fixes:

Severity Issue PriorityScore (*) Exploit Maturity
Prototype Pollution
SNYK-JS-UNSETVALUE-2400660
375/1000
Why? CVSS 7.5
No Known Exploit
Denial of Service (DoS)
SNYK-JS-DECODEURICOMPONENT-3149970
375/1000
Why? CVSS 7.5
Proof of Concept
Validation Bypass
SNYK-JS-KINDOF-537849
375/1000
Why? CVSS 7.5
Proof of Concept

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

Release notes
Package name: grunt-cli from grunt-cli GitHub release notes
Commit messages
Package name: grunt-cli

Compare


Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

@guardrails
Copy link

guardrails bot commented Apr 15, 2023

⚠️ We detected 13 security issues in this pull request:

Vulnerable Libraries (13)
Severity Details
Medium [email protected] (t) upgrade to: >=6.12.3
High [email protected] (t) upgrade to: >2.6.3
Medium [email protected] (t) upgrade to: >=1.2.3
Medium [email protected] (t) upgrade to: >=2.8.9
High [email protected] (t) upgrade to: >=1.3.6
High pkg:npm/[email protected]@2.6.2 (t) upgrade to: 3.2.2,2.6.4
Critical pkg:npm/[email protected]@0.1.0 (t) upgrade to: 1.0.0
High pkg:npm/[email protected]@3.0.4 (t) upgrade to: 3.0.5
High pkg:npm/[email protected]@1.3.5 (t) upgrade to: 1.3.6
Medium pkg:npm/[email protected]@6.10.0 (t) upgrade to: 6.12.3
Critical pkg:npm/[email protected]@4.17.11 (t) upgrade to: 4.17.12,4.17.14,4.17.13,4.5.0,4.6.2,4.6.2,4.6.1
High pkg:npm/[email protected]@2.7.1 (t) - no patch available
Medium pkg:npm/[email protected]@1.2.2 (t) upgrade to: 1.2.3,2.2.1,3.0.1,4.0.3

More info on how to fix Vulnerable Libraries in JavaScript.


👉 Go to the dashboard for detailed results.

📥 Happy? Share your feedback with us.

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.

1 participant