Vulnerability 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 Score
MEDIUM
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Hapijs | Hapi | < 11.0.0 |
Related Weaknesses (CWE)
References
- https://github.com/hapijs/hapi/issues/2840PatchThird Party Advisory
- https://github.com/hapijs/hapi/issues/2850Release NotesThird Party Advisory
- https://nodesecurity.io/advisories/45Third Party Advisory
- https://github.com/hapijs/hapi/issues/2840PatchThird Party Advisory
- https://github.com/hapijs/hapi/issues/2850Release NotesThird Party Advisory
- https://nodesecurity.io/advisories/45Third Party Advisory
FAQ
What is CVE-2015-9236?
CVE-2015-9236 is a vulnerability with a CVSS score of 5.3 (MEDIUM). 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 b...
How severe is CVE-2015-9236?
CVE-2015-9236 has been rated MEDIUM with a CVSS base score of 5.3/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2015-9236?
Check the references section above for vendor advisories and patch information. Affected products include: Hapijs Hapi.