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.
References
Link | Resource |
---|---|
https://github.com/hapijs/hapi/issues/2840 | Patch Third Party Advisory |
https://github.com/hapijs/hapi/issues/2850 | Release Notes Third Party Advisory |
https://nodesecurity.io/advisories/45 | Third Party Advisory |
https://github.com/hapijs/hapi/issues/2840 | Patch Third Party Advisory |
https://github.com/hapijs/hapi/issues/2850 | Release Notes Third Party Advisory |
https://nodesecurity.io/advisories/45 | Third Party Advisory |
Configurations
History
21 Nov 2024, 02:40
Type | Values Removed | Values Added |
---|---|---|
References | () https://github.com/hapijs/hapi/issues/2840 - Patch, Third Party Advisory | |
References | () https://github.com/hapijs/hapi/issues/2850 - Release Notes, Third Party Advisory | |
References | () https://nodesecurity.io/advisories/45 - Third Party Advisory |
Information
Published : 2018-05-31 20:29
Updated : 2024-11-21 02:40
NVD link : CVE-2015-9236
Mitre link : CVE-2015-9236
CVE.ORG link : CVE-2015-9236
JSON object : View
Products Affected
hapijs
- hapi