CVE-2018-3720: Prototype Pollution in assign-deep
Summary
CVE-2018-3720: Prototype Pollution in assign-deep. Affects assign-deep versions < 0.4.7. Fixed in 0.4.7. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
The assign-deep package is an npm package used for deep merging objects. It provides a function that recursively merges the properties of multiple objects into a single object. This package is vulnerable to prototype pollution when merging functions.
Vulnerability Detail
The vulnerability in assign-deep versions before 0.4.7 is due to a lack of proper input validation when merging functions. An attacker can exploit this vulnerability to modify the prototype of objects, leading to potential remote code execution, information disclosure, or denial of service attacks. This can occur when untrusted user input is passed to the assign-deep function, allowing the pollution of the prototype chain and the modification of existing or newly created properties.
How To Fix
Minimum fixed version
0.4.7
This is the first release that contains the fix.
npm install assign-deep@0.4.7Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Workaround
There is no known workaround for this vulnerability. It is recommended to update to the fixed version of the package as soon as possible.
Conclusion
The assign-deep package versions before 0.4.7 are vulnerable to prototype pollution. It is crucial to update to the fixed version to mitigate the risk of remote code execution, information disclosure, or denial of service attacks. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for assign-deep →
FAQ
Prototype pollution is a vulnerability that allows an attacker to modify the prototype of objects, leading to potential security issues.
This vulnerability can lead to remote code execution, information disclosure, or denial of service attacks.
You can use the Vulert Playground (https://vulert.com/scanner) to check if your application is affected by this vulnerability. It analyzes the package-lock.json file and alerts in real-time for open-source vulnerabilities.
Yes, the CVSS score for this vulnerability is 8.8, indicating a high severity.
You can find more information about this vulnerability in the GitHub Advisory Database (https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2018/07/GHSA-xcvv-84j5-jw9h/GHSA-xcvv-84j5-jw9h.json).
Related vulnerabilities
Recent vulnerabilities recorded for assign-deep.
