CVE-2020-28267: Prototype pollution in @strikeentco/set
Summary
CVE-2020-28267: Prototype pollution in @strikeentco/set. Affects @strikeentco/set versions >= 1.0.0, < 1.0.1. Fixed in 1.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
Background
The '@strikeentco/set' package is an npm package that provides a set data structure implementation in JavaScript. It allows users to store and manipulate collections of unique values. The package is widely used in various applications and projects.
Vulnerability Detail
The '@strikeentco/set' package version 1.0.0 is vulnerable to prototype pollution. This vulnerability allows an attacker to modify the prototype of objects, leading to a denial of service and potential remote code execution. By manipulating the prototype, an attacker can introduce malicious behavior or cause the application to crash. This vulnerability has a CVSS score of 7.5, indicating a high severity level.
How To Fix
Minimum fixed version
1.0.1
This is the first release that contains the fix.
npm install @strikeentco/set@1.0.1Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Conclusion
The '@strikeentco/set' package version 1.0.0 is vulnerable to prototype pollution, which can lead to a denial of service and potential remote code execution. Users are advised to upgrade to version 1.0.1 or later to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for @strikeentco/set →
FAQ
Prototype pollution is a vulnerability that allows an attacker to modify the prototype of objects. By manipulating the prototype, an attacker can introduce malicious behavior or cause the application to crash.
The prototype pollution vulnerability in '@strikeentco/set' can lead to a denial of service and potential remote code execution. An attacker could exploit this vulnerability to disrupt the application's functionality or execute arbitrary code on the target system.
Yes, a fix is available in version 1.0.1 of the '@strikeentco/set' package. It is recommended to upgrade to this version or later to mitigate the vulnerability.
To update the '@strikeentco/set' package to version 1.0.1, you can run the following command: npm install @strikeentco/set@1.0.1
No specific workaround is mentioned for this vulnerability. It is recommended to upgrade to the fixed version of the package.
References
Related vulnerabilities
Recent vulnerabilities recorded for @strikeentco/set.
