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 lodash from 4.17.4 to 4.17.21 #18

Merged
merged 1 commit into from
Dec 4, 2024

Conversation

tf-security
Copy link

snyk-top-banner

Snyk has created this PR to fix 9 vulnerabilities in the yarn dependencies of this project.

Snyk changed the following file(s):

  • packages/slate/package.json

Note for zero-installs users

If you are using the Yarn feature zero-installs that was introduced in Yarn V2, note that this PR does not update the .yarn/cache/ directory meaning this code cannot be pulled and immediately developed on as one would expect for a zero-install project - you will need to run yarn to update the contents of the ./yarn/cache directory.
If you are not using zero-install you can ignore this as your flow should likely be unchanged.

⚠️ Warning
Failed to update the yarn.lock, please update manually before merging.

Vulnerabilities that will be fixed with an upgrade:

Issue Score
high severity Prototype Pollution
SNYK-JS-LODASH-608086
  740  
high severity Prototype Pollution
SNYK-JS-LODASH-567746
  635  
high severity Prototype Pollution
SNYK-JS-LODASH-6139239
  600  
high severity Prototype Pollution
SNYK-JS-LODASH-450202
  590  
high severity Prototype Pollution
SNYK-JS-LODASH-73638
  590  
high severity Code Injection
SNYK-JS-LODASH-1040724
  585  
medium severity Prototype Pollution
npm:lodash:20180130
  540  
medium severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-LODASH-1018905
  490  
medium severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-LODASH-73639
  445  

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.
  • This PR was automatically created by Snyk using the credentials of a real user.

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
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic


Learn how to fix vulnerabilities with free interactive lessons:

🦉 Regular Expression Denial of Service (ReDoS)
🦉 Code Injection
🦉 Prototype Pollution

@tf-security tf-security requested a review from a team as a code owner December 4, 2024 10:58
@tf-security
Copy link
Author

tf-security commented Dec 4, 2024

🎉 Snyk checks have passed. No issues have been found so far.

security/snyk check is complete. No issues have been found. (View Details)

license/snyk check is complete. No issues have been found. (View Details)

code/snyk check is complete. No issues have been found. (View Details)

Copy link

gitstream-cm bot commented Dec 4, 2024

This PR is missing a Jira ticket reference in the title or description.
Please add a Jira ticket reference to the title or description of this PR.

Copy link

gitstream-cm bot commented Dec 4, 2024

🥷 Code experts: no user matched threshold 10

See details

packages/slate/package.json

Knowledge based on git-blame:

To learn more about /:\ gitStream - Visit our Docs

@sh-waqar sh-waqar merged commit a33978a into main Dec 4, 2024
9 checks passed
@sh-waqar sh-waqar deleted the snyk-fix-71e725ecbcc92cf319cee7325d8a78fc branch December 4, 2024 11:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants