Quick answers
- Is This vulnerability exploited in the wild?
- No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
- How severe is This vulnerability?
- Informational severity, published 3 September 2020.
- Which products and versions are affected?
- hapi (npm) SEMVER:introduced=0.0.0.
- Is there a fix for This vulnerability?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is This vulnerability attacked?
- It is attacked over the network, in a software library.
- Am I affected?
- Check whether you run hapi (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is a Denial of Service flaw in the CORS request handler of all versions of hapi. When the handler processes invalid values in HTTP headers, it throws an unhandled system exception. If the application lacks proper exception handling, this unhandled error will cause the process to terminate, resulting in service unavailability. An attacker can trigger this by sending requests with malformed CORS-related headers over the network, requiring no authentication or user interaction. The fix is to migrate to @hapi/hapi, the maintained successor package.
Affected products
- hapi hapi All versions
Timeline
- 2020-09-03: disclosed