QID 983805

QID 983805: Nodejs (npm) Security Update for crumb (GHSA-84fq-6626-w5fg)

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.

Successful exploitation of this vulnerability may affect the confidentiality, integrity, and availability of the targeted user.

CVSS V3 rated as Medium - 4.2 severity.

CVSS V2 rated as Medium - 5.8 severity.

Solution

Customers are advised to refer to GHSA-84fq-6626-w5fg for updates pertaining to this vulnerability.

Vendor References

GHSA-84fq-6626-w5fg - github.com/advisories/GHSA-84fq-6626-w5fg

CVEs related to QID 983805

CVE-2014-7193 |

Software Advisories

Advisory ID	Software	Component	Link
GHSA-84fq-6626-w5fg	crumb		github.com/advisories/GHSA-84fq-6626-w5fg

By selecting these links, you may be leaving CVEreport webspace. We have provided these links to other websites because they may have information that would be of interest to you. No inferences should be drawn on account of other sites being referenced, or not, from this page. There may be other websites that are more appropriate for your purpose. CVEreport does not necessarily endorse the views expressed, or concur with the facts presented on these sites. Further, CVEreport does not endorse any commercial products that may be mentioned on these sites. Please address comments about any linked pages to [email protected].