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.
The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
| Link | Tags |
|---|---|
| https://github.com/hapijs/hapi/issues/2850 | third party advisory release notes |
| https://github.com/hapijs/hapi/issues/2840 | third party advisory patch |
| https://nodesecurity.io/advisories/45 | third party advisory |