GHSA-84FQ-6626-W5FG

Vulnerability from github – Published: 2017-10-24 18:33 – Updated: 2020-08-31 18:07
VLAI?
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.

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.

Show details on source website

{
  "affected": [
    {
      "package": {
        "ecosystem": "npm",
        "name": "crumb"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "3.0.0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2014-7193"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-284"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2020-06-16T21:24:14Z",
    "nvd_published_at": "2014-12-25T11:59:00Z",
    "severity": "MODERATE"
  },
  "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.",
  "id": "GHSA-84fq-6626-w5fg",
  "modified": "2020-08-31T18:07:28Z",
  "published": "2017-10-24T18:33:36Z",
  "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"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [],
  "summary": "CORS Token Disclosure in crumb"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.


Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…