Skip to content

CORS Token Disclosure in crumb

Moderate severity GitHub Reviewed Published Oct 24, 2017 to the GitHub Advisory Database • Updated Feb 1, 2023

Package

npm crumb (npm)

Affected versions

< 3.0.0

Patched versions

3.0.0

Description

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.

Recommendation

Update to version 3.0.0 or greater.

References

Published by the National Vulnerability Database Dec 25, 2014
Published to the GitHub Advisory Database Oct 24, 2017
Reviewed Jun 16, 2020
Last updated Feb 1, 2023

Severity

Moderate

EPSS score

0.266%
(67th percentile)

Weaknesses

CVE ID

CVE-2014-7193

GHSA ID

GHSA-84fq-6626-w5fg

Source code

No known source code
Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.