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 |
History
No history.
MITRE Information
Status: PUBLISHED
Assigner: hackerone
Published: 2018-04-26T00:00:00
Updated: 2018-05-31T19:57:01
Reserved: 2017-10-29T00:00:00
Link: CVE-2015-9236
JSON object: View
NVD Information
Status : Modified
Published: 2018-05-31T20:29:00.360
Modified: 2019-10-09T23:15:57.883
Link: CVE-2015-9236
JSON object: View
Redhat Information
No data.