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:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:NHapijs Hapi
APPHapijs< 11.0.0
Related vulnerabilities
hapi is a web and services application framework. When hapi >= 15.0.0 <= 16.1.0 encounters a malformed `accept...
Certain input passed into the If-Modified-Since or Last-Modified headers will cause an 'illegal access' except...
When server level, connection level or route level CORS configurations in hapi node module before 11.1.4 are c...
hoek before 8.5.1 and 9.x before 9.0.3 allows prototype poisoning in the clone function.
hoek node module before 4.2.0 and 5.0.x before 5.0.3 suffers from a Modification of Assumed-Immutable Data (MA...