Description
The Crumb plugin before 3.0.0 for Node.js does not properly restrict token access in situations where a hapi route handler has CORS enabled, which allows remote attackers to obtain sensitive information, and potentially obtain the ability to spoof requests to non-CORS routes, via a crafted web site that is visited by an application consumer.
Analysis and contextual insights are available on OpenCVE Cloud.
Remediation
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
Advisories
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2017-0189 | The Crumb plugin before 3.0.0 for Node.js does not properly restrict token access in situations where a hapi route handler has CORS enabled, which allows remote attackers to obtain sensitive information, and potentially obtain the ability to spoof requests to non-CORS routes, via a crafted web site that is visited by an application consumer. |
Github GHSA |
GHSA-84fq-6626-w5fg | CORS Token Disclosure in crumb |
References
History
No history.
Status: PUBLISHED
Assigner: mitre
Published:
Updated: 2024-08-06T12:40:19.196Z
Reserved: 2014-09-26T00:00:00.000Z
Link: CVE-2014-7193
No data.
Status : Modified
Published: 2014-12-25T11:59:01.413
Modified: 2026-05-06T22:30:45.220
Link: CVE-2014-7193
No data.
OpenCVE Enrichment
No data.
Weaknesses
EUVD
Github GHSA