Security readout for executives and security teams
Plain-English summary
CVE-2017-16117 is a denial-of-service risk in the Node.js slug module. A long, specially crafted string can make the module's regular expression processing block Node's event loop. The public description says about 50,000 characters can pause processing for about two seconds, degrading applications that slugify attacker-controlled text.
Executive priority
Prioritize remediation for internet-facing Node.js services that slugify user-supplied content. This is not evidenced as actively exploited, but it can affect availability and may be easy to trigger where long input is accepted.
Technical view
The issue is classified as CWE-400 resource consumption. A vulnerable regular expression in slug processing can consume CPU synchronously, blocking the single-threaded Node.js event loop. The bundle lists all versions of the slug node module as affected, with no CVSS score and no specific fixed version stated.
Likely exposure
Exposure is most likely in Node.js applications that import the slug module and pass user-controlled strings into slugification paths, such as titles, filenames, usernames, tags, or CMS content. Internal-only use with short trusted strings is lower risk.
Exploitation context
The provided sources do not show known active exploitation, and the CVE is not listed as KEV. Exploitation requires reaching an application path that slugifies untrusted input. The impact is availability degradation rather than code execution or data theft based on the supplied evidence.
Researcher notes
Evidence is limited to the CVE description and linked advisory/issue. The bundle states all versions are affected but does not provide CVSS, a patch version, or exploit-in-the-wild evidence. Treat validation as dependency and data-flow analysis, not exploit reproduction.
Mitigation direction
- Check upstream issue and advisory for current maintainer guidance.
- Avoid passing untrusted long strings directly into slug.
- Enforce conservative input length limits before slugification.
- Consider replacing the dependency if no maintained fix exists.
- Monitor event loop delay and request latency on affected services.
Validation and detection
- Search dependency manifests and lockfiles for the slug package.
- Identify every code path that calls slugification.
- Confirm whether inputs can be user-controlled or externally supplied.
- Test defenses with benign oversized inputs in a controlled environment.
- Review production telemetry for event loop blocking symptoms.
Public sources used
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-16117 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://github.com/dodo/node-slug/issues/82CVE reference · x_refsource_MISC
- https://nodesecurity.io/advisories/537CVE 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.