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-contrib-uglify from 5.0.0 to 5.0.1 #1063

Closed

Conversation

snyk-bot
Copy link

@snyk-bot snyk-bot commented Dec 1, 2021

Snyk has created this PR to upgrade grunt-contrib-uglify from 5.0.0 to 5.0.1.

ℹ️ 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 1 version ahead of your current version.
  • The recommended version was released 8 months ago, on 2021-03-31.

The recommended version fixes:

Severity Issue PriorityScore (*) Exploit Maturity
Denial of Service (DoS)
SNYK-JS-TRIMNEWLINES-1298042
375/1000
Why? CVSS 7.5
No Known Exploit
Command Injection
SNYK-JS-LODASH-1040724
375/1000
Why? CVSS 7.5
Proof of Concept
Arbitrary Code Execution
SNYK-JS-GRUNT-597546
375/1000
Why? CVSS 7.5
No Known Exploit
Prototype Pollution
SNYK-JS-GETOBJECT-1054932
375/1000
Why? CVSS 7.5
No Known Exploit
Regular Expression Denial of Service (ReDoS)
SNYK-JS-LODASH-1018905
375/1000
Why? CVSS 7.5
Proof of Concept
Regular Expression Denial of Service (ReDoS)
SNYK-JS-HOSTEDGITINFO-1088355
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-contrib-uglify from grunt-contrib-uglify GitHub release notes
Commit messages
Package name: grunt-contrib-uglify

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

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