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 underscore.string from 3.3.5 to 3.3.6 #74

Merged
merged 2 commits into from
Jun 10, 2022

Conversation

snyk-bot
Copy link
Contributor

Snyk has created this PR to fix one or more vulnerable packages in the `npm` dependencies of this project.

merge advice

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 589/1000
Why? Has a fix available, CVSS 7.5
Regular Expression Denial of Service (ReDoS)
npm:underscore.string:20170908
No No Known Exploit

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

Commit messages
Package name: underscore.string The new version differs by 9 commits.

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

@farnk05
Copy link
Contributor

farnk05 commented Jun 9, 2022

Is it possible to merge in master and push this security fix after the tests?

@weekens weekens merged commit 96a5fa0 into master Jun 10, 2022
@weekens weekens deleted the snyk-fix-7c3722b1957048b71a840ad8f2e3311d branch June 10, 2022 10:04
@weekens
Copy link
Contributor

weekens commented Jun 10, 2022

Is it possible to merge in master and push this security fix after the tests?

Sure!

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.

3 participants