CVE-2020-28471: Prototype Pollution in properties-reader
Summary
CVE-2020-28471: Properties-Reader before v2.2.0 vulnerable to prototype pollution. Affects properties-reader versions < 2.2.0. Fixed in 2.2.0. 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
properties-reader is an npm package that provides a simple way to read and parse properties files in Node.js applications. It allows developers to easily access and manipulate key-value pairs in properties files. However, versions prior to 2.2.0 are vulnerable to prototype pollution.
Vulnerability Detail
Prototype pollution is a vulnerability that occurs when an attacker can modify the prototype of an object, leading to unexpected behavior or security issues. In the case of properties-reader, an attacker can manipulate the properties file to inject malicious properties that modify the behavior of the application. This can potentially lead to remote code execution, information disclosure, or other security breaches.
How To Fix
Minimum fixed version
2.2.0
This is the first release that contains the fix.
npm install properties-reader@2.2.0Tip — 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 patched version of properties-reader to mitigate the risk of prototype pollution.
Conclusion
In conclusion, properties-reader prior to version 2.2.0 is vulnerable to prototype pollution. This vulnerability can have severe consequences, including remote code execution and information disclosure. It is crucial to update to version 2.2.0 or later to mitigate the risk. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for properties-reader →
FAQ
Prototype pollution is a vulnerability that allows an attacker to modify the prototype of an object, leading to unexpected behavior or security issues.
The consequences of this vulnerability can vary depending on the specific application. However, it can potentially lead to remote code execution, information disclosure, or other security breaches.
You can use Vulert's playground (https://vulert.com/scanner) to check if your application is affected by this vulnerability. Simply upload your package-lock.json file and Vulert will analyze it for open-source vulnerabilities in real-time.
Yes, the fix for this vulnerability is to upgrade properties-reader to version 2.2.0 or later. This version contains a patch that addresses the prototype pollution issue.
No, there are no known workarounds for this vulnerability. It is essential to update to the patched version of properties-reader.
