Medium severity · published May 31, 2018
CVE-2015-9236
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…
5.3
CVSS
1.5%
EPSS
No
On KEV
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 vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Confidentiality
Low
Integrity
None
Availability
None
Scope
Unchanged
Exploitation
Is it being used?
Exploit prediction (EPSS)1.5% · higher than 74% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
HA
Hapi · Hapijs
before 11.0.0 · source: NVD
References
NVD
https://nvd.nist.gov/vuln/detail/CVE-2015-9236
CVE.org
https://www.cve.org/CVERecord?id=CVE-2015-9236
Patch
https://github.com/hapijs/hapi/issues/2840
Release Notes
https://github.com/hapijs/hapi/issues/2850
Third Party Advisory
https://nodesecurity.io/advisories/45
More from Hapi
7.5
CVE-2017-16013
hapi is a web and services application framework
7.5
CVE-2015-9241
Certain input passed into the If-Modified-Since or Last-Modified headers will cause an 'illegal access' exception to be raised
5.9
CVE-2015-9243
When server level, connection level or route level CORS configurations in hapi node module before 11.1.4 are combined and when a higher level config included security restrictions…
