CVE-2015-9236
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.
Does this matter?
Lower severity and a low EPSS score (1.54%). Track it; it rarely justifies an emergency change on its own.
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.
- CVSS 3.0
- 5.3 MEDIUMCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
- EPSS
- 1.54% probability · 73th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-284, CWE-200
- Affected
- hapijs/hapi
- Source
- support@hackerone.com
References
- https://github.com/hapijs/hapi/issues/2840Patch, Third Party Advisory
- https://github.com/hapijs/hapi/issues/2850Release Notes, Third Party Advisory
- https://nodesecurity.io/advisories/45Third Party Advisory
- https://github.com/hapijs/hapi/issues/2840Patch, Third Party Advisory
- https://github.com/hapijs/hapi/issues/2850Release Notes, Third Party Advisory
- https://nodesecurity.io/advisories/45Third Party Advisory
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.