CVE-2015-9243 json
Unsafe Merging of CORS Configuration Conflict in hapi
published 2018-05-29 8 y ago modified 2026-06-17 4 mo ago also GHSA-j3g2-m5jj-6336 , EUVD-2020-1119
- cvss
- 5.9
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.0%
- EPSS 1.0% chance of exploitation in 30 days, percentile 63%
- public exploits
- 0
- none known
Summary
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 (like origin), a higher level config that included security restrictions (like origin) would have those restrictions overridden by less restrictive defaults (e.g. origin defaults to all origins `*`).
Patch / fix
- npm hapi 11.1.4
- hapijs hapi 11.1.4
Exploit prediction
1.00% chance of exploitation in the next 30 days, higher than 63% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- github.com https://github.com/hapijs/hapi/issues/2980 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 5.9 | CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N |
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:N/I:P/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | hapi | <11.1.4 |
11.1.4 |
Affected products
- HackerOne hapi node module
Classification
References
-
github.com
/hapijs/hapi/issues/2980
web, exploit, issue-tracking, third-party-advisory
-
nodesecurity.io
/advisories/65
third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2015-9243
advisory
-
npmjs.com
/advisories/65
web
Sources
- CVE List CVE-2015-9243
- GitHub Advisory GHSA-j3g2-m5jj-6336
- NVD CVE-2015-9243
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.