CVE-2015-9236
Summary
| CVE | CVE-2015-9236 |
|---|---|
| State | PUBLIC |
| Assigner | [email protected] |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2018-05-31 20:29:00 UTC |
| Updated | 2019-10-09 23:15:00 UTC |
| 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. |
Risk And Classification
Problem Types: CWE-200
NVD Known Affected Configurations (CPE 2.3)
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| 11.0.0 Release Notes · Issue #2850 · hapijs/hapi · GitHub | MISC | github.com | Release Notes, Third Party Advisory |
| CORS route-specific override can conflict with connection defaults · Issue #2840 · hapijs/hapi · GitHub | MISC | github.com | Patch, Third Party Advisory |
| Node Security Project | | MISC | nodesecurity.io | Third Party Advisory |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
Legacy QID Mappings
- 984056 Nodejs (npm) Security Update for hapi (GHSA-vwrf-r5r4-7775)