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.

References

• https://nvd.nist.gov/vuln/detail/CVE-2014-7193
• hapijs/crumb@5e6d4f5
• GHSA-84fq-6626-w5fg
• https://www.npmjs.com/advisories/4
• hapijs/crumb@5e6d4f5