CVE-2014-7193 – crumb

Package

Manager: npm
Name: crumb
Vulnerable Version: >=0 <3.0.0

Severity

Level: Medium

CVSS v3.1: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N/E:U/RL:O/RC:C

CVSS v4.0: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

EPSS: 0.00194 pctl0.41531

Details

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.

Metadata

Created: 2017-10-24T18:33:36Z
Modified: 2020-08-31T18:07:28Z
Source: https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2017/10/GHSA-84fq-6626-w5fg/GHSA-84fq-6626-w5fg.json
CWE IDs: ["CWE-284"]
Alternative ID: GHSA-84fq-6626-w5fg
Finding: F039
Auto approve: 1