Security readout for executives and security teams
Plain-English summary
CVE-2017-16113 is an availability risk in the Node.js parsejson module. If an application sends untrusted user input into affected versions, specially crafted input can consume excessive processing time and slow or stop service handling.
Executive priority
Prioritize as a moderate availability issue when parsejson is internet-reachable or used in high-traffic request handling. Lower priority if absent or unreachable.
Technical view
The public record describes a regular expression denial-of-service issue in parsejson versions up to 0.0.3. The weakness is classified as CWE-400, uncontrolled resource consumption. No CVSS score, fixed version, or confirmed exploitation evidence is provided in the supplied sources.
Likely exposure
Exposure is most likely in Node.js applications that directly or transitively depend on parsejson <=0.0.3 and parse user-controlled input with it.
Exploitation context
The bundle does not show CISA KEV listing or active exploitation. Practical risk depends on whether an attacker can reach a parsejson parsing path with untrusted input.
Researcher notes
Evidence is limited to the CVE description, affected version range, CWE, Node Security advisory link, and GitHub issue reference. The sources do not provide CVSS, patch details, or exploitation confirmation.
Mitigation direction
- Inventory direct and transitive parsejson dependencies and flag versions <=0.0.3.
- Check vendor or advisory guidance for a fixed release or supported replacement.
- Remove the dependency where feasible if no maintained fix is available.
- Restrict untrusted input reaching parsejson until the dependency is remediated.
- Use request size and processing safeguards as compensating controls.
Validation and detection
- Review package manifests and lockfiles for parsejson versions <=0.0.3.
- Map application code paths that call parsejson with user-controlled data.
- Confirm exposed routes cannot pass arbitrary input to affected parsing logic.
- Check dependency scanning results against the Node Security advisory.
- Document any accepted residual availability risk and compensating controls.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-400: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2017-16113 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://nodesecurity.io/advisories/528CVE reference · x_refsource_MISC
- https://github.com/get/parsejson/issues/4CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Uncontrolled Resource Consumption
Uncontrolled Resource Consumption represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.