crumb
Affected
- introduced
0, fixed3.0.0(semver)
Fixed versions
3.0.0
Fix
- Fixed version
3.0.0npm install [email protected]
Advisory
Also known as: CVE-2014-7193
CORS Token Disclosure in crumb
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.
Medium Basis: The source's own band: MODERATE
0, fixed 3.0.0 (semver)3.0.0
3.0.0npm install [email protected]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
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0