Security readout for executives and security teams
Plain-English summary
CVE-2018-7651 is a denial-of-service flaw in the Node.js ssri package before 5.2.2. A specially long base64 hash string can make strict-mode parsing consume excessive processing time. Business impact is mainly service slowdown or outage where untrusted data reaches this library path.
Executive priority
Treat as a routine but real availability risk. Prioritize systems that are internet-facing, process user-supplied package metadata or integrity strings, or depend on old Node.js dependency trees.
Technical view
The issue is a regular expression denial of service in ssri index.js before version 5.2.2, triggered through strict mode functionality with a long base64 hash string. The public record does not provide CVSS, CWE, or detailed affected product metadata beyond the ssri module.
Likely exposure
Likely exposure is Node.js applications or tools using ssri before 5.2.2 where attacker-controlled integrity or hash strings can reach strict-mode parsing. Exposure is lower if ssri is updated or that input path is not reachable.
Exploitation context
The source bundle does not show CISA KEV listing or cited evidence of active exploitation. Practical exploitation would require an attacker-controlled long hash string reaching the vulnerable strict-mode parsing path and enough request volume or processing impact to disrupt service.
Researcher notes
Evidence is limited to the CVE record, GitHub issue, fixing commit, and Node Security advisory reference. No CVSS vector, CWE, exploit status, or broad product inventory is provided in the source bundle.
Mitigation direction
- Upgrade ssri to version 5.2.2 or later where feasible.
- Review dependency lockfiles for transitive ssri versions below 5.2.2.
- If immediate upgrade is blocked, check current vendor or maintainer guidance.
- Limit untrusted input reaching strict-mode integrity parsing where practical.
Validation and detection
- Inventory Node.js projects and SBOMs for ssri dependency versions.
- Confirm whether ssri is direct or transitive in production applications.
- Assess whether untrusted integrity or hash strings reach ssri strict mode.
- Verify updated deployments no longer include ssri versions before 5.2.2.
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.
CVE-2018-7651 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/zkat/ssri/commit/d0ebcdc22cb5c8f47f89716d08b3518b2485d65dCVE reference · x_refsource_CONFIRM
- https://github.com/zkat/ssri/issues/10CVE reference · x_refsource_CONFIRM
- https://nodesecurity.io/advisories/565CVE reference · x_refsource_CONFIRM
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.