CVE-2015-9236
Incorrect handling of CORS preflight request headers in hapi
Overview
Description
Hapi versions less than 11.0.0 implement CORS incorrectly and allowed for configurations that at best returned inconsistent headers and at worst allowed cross-origin activities that were expected to be forbidden. If the connection has CORS enabled but one route has it off, and the route is not GET, the OPTIONS prefetch request will return the default CORS headers and then the actual request will go through and return no CORS headers. This defeats the purpose of turning CORS on the route.
Source: OX vulnerability database
Severity
5.3 · MEDIUM
CVSS 3.0 base score, scored by NVD.
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Weakness: CWE-284, CWE-200
Affected packages · 1
| Ecosystem | Package | Vulnerable | Fixed in |
|---|---|---|---|
| npm | hapi | <11.0.0 | 11.0.0 |
Open a package to see all its vulnerabilities.
Operating systems
No Linux distribution reports this ID.
References
- github.com https://github.com/advisories/GHSA-vwrf-r5r4-7775
- github.com https://github.com/hapijs/hapi/issues/2840
- github.com https://github.com/hapijs/hapi/issues/2850
- nodesecurity.io https://nodesecurity.io/advisories/45
- nvd.nist.gov https://nvd.nist.gov/vuln/detail/CVE-2015-9236
- www.npmjs.com https://www.npmjs.com/advisories/45
OX Radar and Response Center
Find threats in your stack.
OX Radar can check high-priority threats, like critical package CVEs, against your context.
Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.