Advisory

GHSA-84fq-6626-w5fg

Also known as: CVE-2014-7193

Summary

CORS Token Disclosure in crumb

Details

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.

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2017-10-24 18:33 UTC
Modified
2023-11-08 03:57 UTC

Affected packages and fixes

crumb

npm · All systems

Affected

  • introduced 0, fixed 3.0.0 (semver)

Fixed versions

3.0.0

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences