GHSA-84fq-6626-w5fg
Suggest an improvement- Source
- https://github.com/advisories/GHSA-84fq-6626-w5fg
- Import Source
- https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2017/10/GHSA-84fq-6626-w5fg/GHSA-84fq-6626-w5fg.json
- JSON Data
- https://api.osv.dev/v1/vulns/GHSA-84fq-6626-w5fg
- Aliases
-
- CVE-2014-7193
- Published
- 2017-10-24T18:33:36Z
- Modified
- 2023-11-08T03:57:44Z
- 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.
- Database specific
{ "cwe_ids": [ "CWE-284" ], "github_reviewed": true, "github_reviewed_at": "2020-06-16T21:24:14Z", "nvd_published_at": "2014-12-25T11:59:00Z", "severity": "MODERATE" }- References
Affected packages
npm / crumb
Package
- Name
- crumb
- View open source insights on deps.dev
- Purl
- pkg:npm/crumb