CVE-2019-10745 json
assign-deep Vulnerable to Prototype Pollution
published 2019-08-20 7 y ago modified 2026-06-17 4 mo ago also GHSA-66rh-8fw6-59q6 , EUVD-2019-0624
- cvss
- 7.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.1%
- EPSS 1.1% chance of exploitation in 30 days, percentile 66%
- public exploits
- 0
- none known
Summary
assign-deep is vulnerable to Prototype Pollution in versions before 0.4.8 and version 1.0.0. The function assign-deep could be tricked into adding or modifying properties of Object.prototype using either a constructor or a _proto_ payload.
Patch / fix
- npm assign-deep 0.4.8, 1.0.1
- assign-deep_project assign-deep 0.4.8
Exploit prediction
1.14% chance of exploitation in the next 30 days, higher than 66% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- snyk.io https://snyk.io/vuln/SNYK-JS-ASSIGNDEEP-450211 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:P/A:N |
| GitHub | 3.0 | 7.5 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | assign-deep | <0.4.8 >=1.0.0, <1.0.1 |
0.4.8 1.0.1 |
Affected products
- n/a assign-deep
Classification
References
-
snyk.io
/vuln/SNYK-JS-ASSIGNDEEP-450211
web, exploit, patch, third-party-advisory
-
github.com
/jonschlinkert/assign-deep/commit/8e3cc4a34246733672c71e96532105384937e56c
web
-
github.com
/jonschlinkert/assign-deep/commit/90bf1c551d05940898168d04066bbf15060f50cc
web
-
nvd.nist.gov
/vuln/detail/CVE-2019-10745
advisory
-
github.com
/jonschlinkert/assign-deep
package
-
npmjs.com
/advisories/1014
web
Sources
- CVE List CVE-2019-10745
- GitHub Advisory GHSA-66rh-8fw6-59q6
- NVD CVE-2019-10745
Fencer Vulns 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.