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 lodash from 4.17.20 to 4.17.21 #24

Merged

Conversation

snyk-bot
Copy link
Contributor

Snyk has created this PR to upgrade lodash from 4.17.20 to 4.17.21.

merge advice
ℹ️ 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 4 months ago, on 2021-02-20.

The recommended version fixes:

Severity Issue PriorityScore (*) Exploit Maturity
Command Injection
SNYK-JS-LODASH-1040724
681/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 7.2
Proof of Concept
Regular Expression Denial of Service (ReDoS)
SNYK-JS-LODASH-1018905
681/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 7.2
Proof of Concept

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

Release notes
Package name: lodash from lodash GitHub release notes
Commit messages
Package name: lodash

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

@cthompson-dwolla cthompson-dwolla merged commit b85a1a7 into master Nov 4, 2021
@cthompson-dwolla cthompson-dwolla deleted the snyk-upgrade-002f8853de124dea595f60ccee152902 branch November 4, 2021 13:58
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