Advisory Database
  • Advisories
  • Dependency Scanning
  1. npm
  2. ›
  3. crumb
  4. ›
  5. GMS-2014-18

GMS-2014-18: Token Disclosure

August 1, 2014

When CORS is enabled on a hapi route handler, it is possible to set a crumb token for a different domain. An attacker would need to have an application consumer visit a site they control, request a route supporting CORS, and then retrieve the token. With this token, they could possibly make requests to non CORS routes as this user. A configuration and scenario where this would occur is unlikely, as most configurations will set CORS globally (where crumb is not used), or not at all.

References

  • github.com/spumko/crumb/commit/5e6d4f5c81677fe9e362837ffd4a02394303db3c

Code Behaviors & Features

Detect and mitigate GMS-2014-18 with GitLab Dependency Scanning

Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Dependency Scanning using SBOM also detects vulnerabilities from proprietary advisories that this site does not include. Learn more about Dependency Scanning using SBOM →

Affected versions

All versions before 3.0.0

Fixed versions

  • 3.0.0

Solution

Update to a version 3.0.0 or greater.

Source file

npm/crumb/GMS-2014-18.yml

Spotted a mistake? Edit the file on GitLab.

  • Site Repo
  • About GitLab
  • Terms
  • Privacy Statement
  • Contact

Page generated Sun, 08 Nov 2026 00:17:25 +0000.