CVE-2015-9236

Published May 31, 2018 CVSS 3.0 · 5.3 Medium EPSS 1.5% KEV · Not listed
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.

Remediation

No solution or workaround provided in the CVE record

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
EUVD EUVD EUVD-2018-0202 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.
Github GHSA Github GHSA GHSA-vwrf-r5r4-7775 Incorrect handling of CORS preflight request headers in hapi
History

No history.

Weaknesses

Sources

Status
PUBLISHED
Assigner
hackerone
Published
Updated
Sep 17, 2024, 4:15 AM
Reserved
Oct 29, 2017, 12:00 AM
Status
Modified
Published
May 31, 2018, 8:29 PM
Modified
Jun 17, 2026, 12:36 AM