CVE-2020-28273: Prototype Pollution in set-in
Summary
CVE-2020-28273: Prototype pollution in set-in. Affects set-in versions < 2.0.1. Fixed in 2.0.1. 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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The 'set-in' package is an npm package that provides a utility function for setting nested properties in JavaScript objects. It is commonly used to manipulate and update object properties in a convenient way. However, versions 1.0.0 through 2.0.0 of the 'set-in' package are vulnerable to prototype pollution.
Vulnerability Detail
The vulnerability in 'set-in' versions 1.0.0 through 2.0.0 is due to prototype pollution. An attacker can exploit this vulnerability to cause a denial of service and potentially execute remote code. Prototype pollution occurs when an attacker can modify the prototype of an object, leading to unexpected behavior and potential security issues. In this case, the 'set-in' package does not properly validate user input, allowing an attacker to manipulate the prototype chain and execute arbitrary code.
How To Fix
Minimum fixed version
2.0.1
This is the first release that contains the fix.
npm install set-in@2.0.1Tip — 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 crucial to update to the latest version of the 'set-in' package to mitigate the risk.
Conclusion
The 'set-in' package versions 1.0.0 through 2.0.0 are vulnerable to prototype pollution, which can lead to a denial of service and potential remote code execution. It is crucial to update to version 2.0.1 or later to mitigate the risk. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for set-in →
FAQ
Prototype pollution is a vulnerability that allows an attacker to modify the prototype of an object, leading to unexpected behavior and potential security issues.
This vulnerability in 'set-in' can result in a denial of service and potentially remote code execution, allowing an attacker to take control of the affected system.
Versions 1.0.0 through 2.0.0 of the 'set-in' package are affected by this vulnerability.
You can use the Vulert Playground (https://vulert.com/scanner) to check if your application is affected by this vulnerability. Simply upload your package-lock.json file and the tool will alert you if any vulnerabilities are found.
Yes, upgrading to version 2.0.1 or later of the 'set-in' package will fix this vulnerability. Make sure to update your package by running 'npm install set-in@latest'.
Related vulnerabilities
Recent vulnerabilities recorded for set-in.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
