ghsa-j3g2-m5jj-6336
Vulnerability from github
Published
2020-09-01 15:20
Modified
2020-08-31 18:09
Summary
Unsafe Merging of CORS Configuration Conflict in hapi
Details

Versions of hapi prior to 11.1.4 are affected by a vulnerability that causes route-level CORS configuration to override connection-level or server-level CORS defaults. This may result in a situation where CORS permissions are less restrictive than intended.

Recommendation

Update hapi to version 11.1.4 or later.

Show details on source website


{
  "affected": [
    {
      "package": {
        "ecosystem": "npm",
        "name": "hapi"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "11.1.4"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2015-9243"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-284"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2020-08-31T18:09:51Z",
    "nvd_published_at": null,
    "severity": "MODERATE"
  },
  "details": "Versions of `hapi` prior to 11.1.4 are affected by a vulnerability that causes route-level CORS configuration to override connection-level or server-level CORS defaults. This may result in a situation where CORS permissions are less restrictive than intended.\n\n\n\n\n## Recommendation\n\nUpdate hapi to version 11.1.4 or later.",
  "id": "GHSA-j3g2-m5jj-6336",
  "modified": "2020-08-31T18:09:51Z",
  "published": "2020-09-01T15:20:00Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2015-9243"
    },
    {
      "type": "WEB",
      "url": "https://github.com/hapijs/hapi/issues/2980"
    },
    {
      "type": "WEB",
      "url": "https://www.npmjs.com/advisories/65"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [],
  "summary": "Unsafe Merging of CORS Configuration Conflict in hapi"
}


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 seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.


Loading…

Loading…