CVE-2019-10747 json
Prototype Pollution in set-value
published 7y ago modified last mo. also GHSA-4g88-fppr-53pp , EUVD-2019-0617
- cvss
- 9.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.5%
- EPSS 2.5% chance of exploitation in 30 days, percentile 84%
- public exploits
- 0
- none known
Summary
set-value is vulnerable to Prototype Pollution in versions lower than 3.0.1. The function mixin-deep could be tricked into adding or modifying properties of Object.prototype using any of the constructor, prototype and _proto_ payloads.
Patch / fix
- npm set-value 2.0.1, 3.0.1
- set-value_project set-value 2.0.1, 3.0.1
- node-set-value Debian 14, Debian 13, Debian 12 0.4.0-2
debian advisories DEBIAN-CVE-2019-10747
- rh-nodejs12-nodejs RHEL 3 SOFTWARE_COLLECTIONS 12.20.1-1.el7
- rh-nodejs12-npm RHEL 3 SOFTWARE_COLLECTIONS 6.14.10-12.20.1.1.el7
- rh-nodejs12-nodejs-nodemon RHEL 3 SOFTWARE_COLLECTIONS 2.0.3-1.el7
- npm RHEL 8 1:6.14.10-1.12.20.1.1.module+el8.3.0+9503+19cb079c
- nodejs RHEL 8 1:12.20.1-1.module+el8.3.0+9503+19cb079c
- nodejs-nodemon RHEL 8 2.0.3-1.module+el8.3.0+9715+1718613f
- nodejs-full-i18n RHEL 8 1:12.20.1-1.module+el8.3.0+9503+19cb079c
- nodejs-packaging RHEL 8 17-3.module+el8.1.0+3369+37ae6a45
red hat advisories RHSA-2021:0485RHSA-2021:0549
- nodejs-nodemon AlmaLinux 8 2.0.3-1.module_el8.4.0+2521+c668cc9f
- nodejs-packaging AlmaLinux 8 17-3.module_el8.4.0+2224+b07ac28e
- nodejs-packaging AlmaLinux 8 17-3.module_el8.4.0+2521+c668cc9f
- nodejs-packaging AlmaLinux 8 17-3.module_el8.3.0+2023+d2377ea3
almalinux advisories ALSA-2021:0549
- nodejs-nodemon Rocky Linux 8 2.0.3-1.module+el8.6.0+982+9fdca2d4
- nodejs-nodemon Rocky Linux 8 2.0.3-1.module+el8.3.0+100+234774f7
- nodejs-nodemon Rocky Linux 8 2.0.3-1.module+el8.4.0+638+5344c6f7
- nodejs-packaging Rocky Linux 8 17-3.module+el8.3.0+101+f84c7154
rocky linux advisories RLSA-2021:0549
Is CVE-2019-10747 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2019-10747 updated cvss 4.2
nodejs-set-value: prototype pollution in function set-value
-
Red Hat Enterprise Linux 8 nodejs-nodemonaffected: no fix available “Fix deferred”
-
Red Hat OpenShift Container Platform 3.11 kibana Red Hat OpenShift Container Platform 4 kibanaaffected: no fix planned “Will not fix”
-
Red Hat OpenShift distributed tracing 2 rhosdt/jaeger-all-in-one-rhel8 Red Hat Software Collections rh-nodejs10-nodejs-nodemonaffected: no fix available “Fix deferred”
-
Red Hat Enterprise Linux AppStream (v. 8) nodejs 12.20.1-1.module+el8.3.0+9503+19cb079c, nodejs-packaging 17-3.module+el8.1.0+3369+37ae6a45, nodejs-nodemon 2.0.3-1.module+el8.3.0+9715+1718613f, npm 6.14.10-1.12.20.1.1.module+el8.3.0+9503+19cb079c, nodejs-full-i18n 12.20.1-1.module+el8.3.0+9503+19cb079cfixed: vendor fix RHSA-2021:0549
-
Red Hat Software Collections for Red Hat Enterprise Linux Server (v. 7) rh-nodejs12-nodejs 12.20.1-1.el7, rh-nodejs12-npm 6.14.10-12.20.1.1.el7, rh-nodejs12-nodejs-nodemon 2.0.3-1.el7 Red Hat Software Collections for Red Hat Enterprise Linux Server EUS (v. 7.6) rh-nodejs12-nodejs 12.20.1-1.el7, rh-nodejs12-npm 6.14.10-12.20.1.1.el7, rh-nodejs12-nodejs-nodemon 2.0.3-1.el7 Red Hat Software Collections for Red Hat Enterprise Linux Server EUS (v. 7.7) rh-nodejs12-nodejs 12.20.1-1.el7, rh-nodejs12-npm 6.14.10-12.20.1.1.el7, rh-nodejs12-nodejs-nodemon 2.0.3-1.el7 Red Hat Software Collections for Red Hat Enterprise Linux Workstation (v. 7) rh-nodejs12-nodejs 12.20.1-1.el7, rh-nodejs12-npm 6.14.10-12.20.1.1.el7, rh-nodejs12-nodejs-nodemon 2.0.3-1.el7fixed: vendor fix RHSA-2021:0485
-
Red Hat Quay 3 nodejs-set-valuenot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
2.48% chance of exploitation in the next 30 days, higher than 84% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- snyk.io https://snyk.io/vuln/SNYK-JS-SETVALUE-450213 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
| GitHub | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | set-value | <2.0.1 >=3.0.0, <3.0.1 |
2.0.1 3.0.1 |
Affected products
- n/a set-value
Classification
References
-
github.com
/jonschlinkert/set-value/commit/95e9d9923f8a8b4a01da1ea138fcc39ec7b6b15f
web
-
github.com
/jonschlinkert/set-value/commit/cb12f14955dde6e61829d70d1851bfea6a3c31ad
web
-
snyk.io
/vuln/SNYK-JS-SETVALUE-450213
web, exploit, third-party-advisory
-
lists.fedoraproject.org
/archives/list/package-announce%40lists.fedoraproject.org/message/3EJ36KV6MXQPUYTFCCTDY54E5Y7QP3AV/
vendor-advisory
-
lists.fedoraproject.org
/archives/list/package-announce%40lists.fedoraproject.org/message/E3HNLQZQINMZK6GYB2UTKK4VU7WBV2OT/
vendor-advisory
-
lists.apache.org
/thread.html/b46f35559c4a97cf74d2dd7fe5a48f8abf2ff37f879083920af9b292%40%3Cdev.drat.apache.org%3E
mailing-list
-
nvd.nist.gov
/vuln/detail/CVE-2019-10747
advisory
-
lists.apache.org
/thread.html/b46f35559c4a97cf74d2dd7fe5a48f8abf2ff37f879083920af9b292@%3Cdev.drat.apache.org%3E
web
-
lists.fedoraproject.org
/archives/list/package-announce@lists.fedoraproject.org/message/3EJ36KV6MXQPUYTFCCTDY54E5Y7QP3AV
web
-
lists.fedoraproject.org
/archives/list/package-announce@lists.fedoraproject.org/message/E3HNLQZQINMZK6GYB2UTKK4VU7WBV2OT
web
-
npmjs.com
/advisories/1012
web
Sources
- CVE List CVE-2019-10747
- GitHub Advisory GHSA-4g88-fppr-53pp
- NVD CVE-2019-10747
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.