CVE-2019-10808 json
Improperly Controlled Modification of Dynamically-Determined Object Attributes in utilitify
published 6y ago modified 4mo ago also GHSA-9534-h433-2rjf , EUVD-2021-1025
- cvss
- 8.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.0%
- EPSS 2.0% chance of exploitation in 30 days, percentile 81%
- public exploits
- 0
- none known
Summary
utilitify prior to 1.0.3 allows modification of object properties. The merge method could be tricked into adding or modifying properties of the Object.prototype.
Patch / fix
- npm utilitify 1.0.3
- xcritical.software utilitify 1.0.3
Is CVE-2019-10808 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
2.04% chance of exploitation in the next 30 days, higher than 81% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- snyk.io https://snyk.io/vuln/SNYK-JS-UTILITIFY-559497 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 6.5 | AV:N/AC:L/Au:S/C:P/I:P/A:P |
| GitHub | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | utilitify | <1.0.3 |
1.0.3 |
Affected products
- n/a utilitify
Classification
References
- github.com /xcritical-software/utilitify/commit/88d6e27009823338bf319ffb768fe6b08e8ad2d1%2C
-
snyk.io
/vuln/SNYK-JS-UTILITIFY-559497
web, exploit, patch, third-party-advisory
-
github.com
/xcritical-software/utilitify/commit/88d6e27009823338bf319ffb768fe6b08e8ad2d1,
web
-
nvd.nist.gov
/vuln/detail/CVE-2019-10808
advisory
Sources
- CVE List CVE-2019-10808
- GitHub Advisory GHSA-9534-h433-2rjf
- NVD CVE-2019-10808
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.