CVE-2017-16113 json
Regular Expression Denial of Service in parsejson
published 2018-06-07 8 y ago modified 2026-06-17 4 mo ago also GHSA-q75g-2496-mxpp , EUVD-2018-0311
- cvss
- 7.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.5%
- EPSS 1.5% chance of exploitation in 30 days, percentile 74%
- public exploits
- 0
- none known
Summary
The parsejson module is vulnerable to regular expression denial of service when untrusted user input is passed into it to be parsed.
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2017-16113 updated cvss 7.5
nodejs-parsejson: Regular Denial of Service
-
Red Hat Quay 3 quay/quay-rhel8 Red Hat Virtualization 4 ovirt-engine-dashboardnot 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
1.49% chance of exploitation in the next 30 days, higher than 74% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- github.com https://github.com/get/parsejson/issues/4 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 7.5 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:N/A:P |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | parsejson | <=0.0.3 |
no fix listed |
Affected products
- HackerOne parsejson node module
Classification
References
-
github.com
/get/parsejson/issues/4
web, exploit, issue-tracking, third-party-advisory
-
nodesecurity.io
/advisories/528
third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2017-16113
advisory
-
github.com
/advisories/GHSA-q75g-2496-mxpp
advisory
-
npmjs.com
/advisories/528
web
Sources
- CVE List CVE-2017-16113
- GitHub Advisory GHSA-q75g-2496-mxpp
- NVD CVE-2017-16113
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.