First published: Thu Jun 20 2019(Updated: )
A flaw was found in nodejs-set-value. The function mixin-deep can be tricked into adding or modifying properties of Object.prototype using any of the constructor, prototype, or _proto_ payloads. The highest threat from this vulnerability is to data confidentiality and integrity.
Credit: report@snyk.io report@snyk.io
Affected Software | Affected Version | How to fix |
---|---|---|
npm/set-value | =3.0.0 | 3.0.1 |
npm/set-value | <2.0.1 | 2.0.1 |
IBM Cloud Pak for Security (CP4S) | <=1.6.0.1 | |
IBM Cloud Pak for Security (CP4S) | <=1.6.0.0 | |
IBM Cloud Pak for Security (CP4S) | <=1.5.0.1 | |
IBM Cloud Pak for Security (CP4S) | <=1.5.0.0 | |
IBM Cloud Pak for Security (CP4S) | <=1.4.0.0 | |
Set-value Project Set-value | <2.0.1 | |
Set-value Project Set-value | >=3.0.0<3.0.1 | |
redhat/rh-nodejs12-nodejs | <0:12.20.1-1.el7 | 0:12.20.1-1.el7 |
redhat/rh-nodejs12-nodejs-nodemon | <0:2.0.3-1.el7 | 0:2.0.3-1.el7 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2019-10747 is a vulnerability in the Node.js set-value module that allows for prototype pollution.
CVE-2019-10747 has a severity rating of 9.8 (Critical).
CVE-2019-10747 can be exploited by sending a specially-crafted request using a constructor payload.
The affected software for CVE-2019-10747 includes Node.js set-value module versions lower than 3.0.1, IBM Cloud Pak for Security (CP4S) versions up to 1.6.0.1, and others.
The vulnerability in CVE-2019-10747 can be fixed by updating to version 3.0.1 of the Node.js set-value module or applying the appropriate remedy provided by the vendor.