CVE-2019-10750 json
Prototype Pollution in deeply
published 7y ago modified 4mo ago also GHSA-8j4w-5fw4-rm27 , EUVD-2019-0628
- cvss
- 9.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.7%
- EPSS 1.7% chance of exploitation in 30 days, percentile 77%
- public exploits
- 0
- none known
Summary
deeply is vulnerable to Prototype Pollution in versions before 3.1.0. The function assign-deep could be tricked into adding or modifying properties of Object.prototype using using a _proto_ payload.
Patch / fix
- npm deeply 3.1.0
- deeply_project deeply 3.1.0
Is CVE-2019-10750 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 FencerExploit prediction
1.69% chance of exploitation in the next 30 days, higher than 77% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- snyk.io https://snyk.io/vuln/SNYK-JS-DEEPLY-451026 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 | deeply | <3.1.0 |
3.1.0 |
Affected products
- n/a deeply
Classification
- Weakness
-
- CWE-400 Uncontrolled Resource Consumption
References
-
snyk.io
/vuln/SNYK-JS-DEEPLY-451026
web, exploit, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2019-10750
advisory
-
npmjs.com
/advisories/1030
web
Sources
- CVE List CVE-2019-10750
- GitHub Advisory GHSA-8j4w-5fw4-rm27
- NVD CVE-2019-10750
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.