Fix: Upgrade lodash to address Prototype Pollution vulnerability #1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix: Upgrade lodash to address Prototype Pollution vulnerability
Vulnerability Details
Summary of Changes
This pull request upgrades the
lodashdependency from version 4.17.4 to 4.17.21 to address a High severity Prototype Pollution vulnerability.What was changed:
lodashversion inpackage.jsonfrom4.17.4to4.17.21package-lock.jsonwith the new dependency treeVulnerability Background
Prototype Pollution is a vulnerability that affects JavaScript applications when an attacker can inject properties into existing JavaScript language construct prototypes, such as objects. This can lead to denial of service, remote code execution, or property injection attacks.
The lodash library versions prior to 4.17.21 contained prototype pollution vulnerabilities that have been patched in the newer version.
Testing Status
npm installcompleted successfully with the new lodash versionnpm testcould not be executed due to Snyk authentication requirementsVerification Steps
npm installto update dependencies - completed successfullyRisk Assessment
References
Link to Devin run: https://app.devin.ai/sessions/5c328ccccdee4dd78281a28848eab8bf
Requested by: Shawn Azman ([email protected])
This PR follows the Snyk Vulnerability Remediation Playbook for addressing security vulnerabilities in dependencies.