Which versions of crumb are affected by CVE-2014-7193?

crumb (npm) versions < 3.0.0 is affected.

Is there a fix for CVE-2014-7193?

Yes. CVE-2014-7193 is fixed in 3.0.0. Upgrade to this version or later.

Is CVE-2014-7193 exploitable, and should I be worried?

Whether CVE-2014-7193 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2014-7193 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2014-7193?

Upgrade crumb to 3.0.0 or later.

CVE-2014-7193 in crumb

Q: What is CVE-2014-7193?

CVE-2014-7193 is a medium-severity security vulnerability in crumb (npm), affecting versions < 3.0.0. It is fixed in 3.0.0.

Q: Is there a fix for CVE-2014-7193?

Yes. CVE-2014-7193 is fixed in 3.0.0. Upgrade to this version or later.

Q: Is CVE-2014-7193 exploitable, and should I be worried?

Whether CVE-2014-7193 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2014-7193 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2014-7193?

Upgrade crumb to 3.0.0 or later.

CVE-2014-7193

CVE-2014-7193 is a medium-severity security vulnerability in crumb (npm), affecting versions < 3.0.0. It is fixed in 3.0.0.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!

Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

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.

Impact

Affected versions

crumb (< 3.0.0)

Security releases

crumb → 3.0.0 (npm)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Update to version 3.0.0 or greater.

Frequently Asked Questions

What is CVE-2014-7193? CVE-2014-7193 is a medium-severity security vulnerability in crumb (npm), affecting versions < 3.0.0. It is fixed in 3.0.0.
Which versions of crumb are affected by CVE-2014-7193? crumb (npm) versions < 3.0.0 is affected.
Is there a fix for CVE-2014-7193? Yes. CVE-2014-7193 is fixed in 3.0.0. Upgrade to this version or later.
Is CVE-2014-7193 exploitable, and should I be worried? Whether CVE-2014-7193 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2014-7193 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2014-7193? Upgrade crumb to 3.0.0 or later.