Security readout for executives and security teams
Plain-English summary
This affects old Node.js hapi applications using the Crumb CSRF plugin before 3.0.0. If CORS is enabled on a route, a malicious website visited by an application user may obtain a CSRF token and weaken protection on other routes.
Executive priority
Prioritize remediation for internet-facing legacy hapi applications that use Crumb and browser authentication. The issue is older, but it can undermine CSRF defenses where the vulnerable pattern exists.
Technical view
Crumb before 3.0.0 did not properly restrict token access when a hapi route handler had CORS enabled. The CVE says this can disclose sensitive token data and potentially allow request spoofing against non-CORS routes.
Likely exposure
Exposure is likely limited to legacy hapi applications using Crumb before 3.0.0 with CORS-enabled routes reachable by authenticated browser users.
Exploitation context
The source describes a crafted website visited by an application consumer. KEV is false, and the supplied sources do not show active exploitation in the wild.
Researcher notes
The public bundle lacks CVSS, CWE, and detailed affected CPE data. Analysis should stay scoped to Crumb before 3.0.0 for Node.js hapi, specifically where CORS-enabled handlers expose token access.
Mitigation direction
- Inventory hapi applications for the Crumb plugin and installed versions.
- Upgrade Crumb to 3.0.0 or later, following vendor guidance.
- Review CORS-enabled routes for unnecessary token exposure.
- Restrict trusted origins where CORS remains required.
- Retest CSRF protection after dependency and CORS changes.
Validation and detection
- Check package manifests and lockfiles for Crumb versions before 3.0.0.
- Identify hapi route handlers with CORS enabled.
- Confirm CORS responses do not expose CSRF tokens to untrusted origins.
- Verify protected non-CORS routes still reject unauthorized cross-origin requests.
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.
Credential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2014-7193 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/crumb_cors_token_disclosureCVE reference · x_refsource_CONFIRM
- https://github.com/hapijs/crumb/commit/5e6d4f5c81677fe9e362837ffd4a02394303db3cCVE 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.