Vulnerabilities in pkg:npm/crumb

PACKAGE
Advisory Identifier: GHSA-84fq-6626-w5fg
Advisory Summary

CVE-2014-7193 is a MODERATE cors token disclosure vulnerability (CWE-284: Improper Access Control) affecting Crumb libraries in the npm ecosystem. The issue involves cors token disclosure in crumb. Remediation is available by upgrading affected packages to version 3.0.0.

1 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:npm/crumb

1 Known Advisory Record(s)

Vulnerability advisories affecting package pkg:npm/crumb. Select an advisory below to view technical details or fixes.

Advisory ID CVE / NVD Severity Summary
GHSA-84fq-6626-w5fg CVE-2014-7193 MODERATE CORS Token Disclosure in crumb

CVE-2014-7193 at a Glance

CVE Identifier CVE-2014-7193
GHSA Identifier GHSA-84fq-6626-w5fg
Severity MODERATE
CVSS v3.1 Base Score N/A
CWE Classification CWE-284: Improper Access Control
Affected Product Crumb
Package Ecosystem npm
Published Date
Last Updated

How to Fix CVE-2014-7193

To remediate this vulnerability, upgrade all affected Crumb dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

crumb fixed: 3.0.0
npm install crumb@3.0.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls crumb

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2014-7193, inspect your project dependencies using npm:

npm ls crumb

Analyze the terminal output to locate any version of Crumb in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 3.0.0), your application is affected.

Note: The npm ls crumb command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-284: Improper Access Control, where the product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. In Crumb, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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.

CVE-2014-7193 Affected Crumb Versions

1 component(s)
Fixed Versions:
3.0.0
Product / Package Ecosystem Affected Versions Fixed Version
crumb
npm
< 3.0.0
3.0.0

References

Frequently Asked Questions

What is CVE-2014-7193?
CVE-2014-7193 is a security vulnerability in Crumb involving CORS Token Disclosure in crumb under CWE-284: Improper Access Control.
Which Crumb versions are affected?
Affected versions include releases prior to 3.0.0 across affected packages: crumb.
What version fixes CVE-2014-7193?
Upgrading to 3.0.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is crumb affected?
Yes, crumb is affected in releases prior to 3.0.0. Upgrade your dependency to 3.0.0 or later.
What CWE is associated with CVE-2014-7193?
CVE-2014-7193 is classified under CWE-284: Improper Access Control (The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.).
How can I check npm dependencies for CVE-2014-7193?
Run the dependency tree command: 'npm ls crumb'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-84fq-6626-w5fg",
  "modified" : "2020-08-31T18:07:28Z",
  "published" : "2017-10-24T18:33:36Z",
  "aliases" : [ "CVE-2014-7193" ],
  "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.\n\nA 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.\n\n\n## Recommendation\n\nUpdate to version 3.0.0 or greater.",
  "severity" : [ ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "crumb"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "3.0.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2014-7193"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/hapijs/crumb/commit/5e6d4f5c81677fe9e362837ffd4a02394303db3c"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/spumko/crumb/commit/5e6d4f5c81677fe9e362837ffd4a02394303db3c"
  }, {
    "type" : "ADVISORY",
    "url" : "https://github.com/advisories/GHSA-84fq-6626-w5fg"
  }, {
    "type" : "WEB",
    "url" : "https://www.npmjs.com/advisories/4"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-284" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2020-06-16T21:24:14Z",
    "nvd_published_at" : "2014-12-25T11:59:00Z"
  }
}