How severe is GHSA-66mv-xh68-h6v2?

No CVSS score has been assigned to GHSA-66mv-xh68-h6v2 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-66mv-xh68-h6v2?

GHSA-66mv-xh68-h6v2 affects the following packages: @commercial/hapi (npm), @commercial/hapi (npm), @commercial/hapi (npm), @commercial/hapi (npm). Ecosystems affected: npm.

How do I fix GHSA-66mv-xh68-h6v2?

Update @commercial/hapi to 16.8.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-66mv-xh68-h6v2 is resolved across your whole dependency graph.

How do I detect GHSA-66mv-xh68-h6v2 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @commercial/hapi. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-66mv-xh68-h6v2 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-66mv-xh68-h6v2?

O3 pinpoints whether GHSA-66mv-xh68-h6v2 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-66mv-xh68-h6v2 actively exploited in the wild?

No public exploit code has been indexed for GHSA-66mv-xh68-h6v2 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-66mv-xh68-h6v2 published, and has it been updated?

GHSA-66mv-xh68-h6v2 was published on September 3, 2020 and was last updated on August 31, 2020. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

GHSA-66mv-xh68-h6v2

GHSA-66mv-xh68-h6v2 is a security vulnerability in @commercial/hapi. O3 Security confirms whether GHSA-66mv-xh68-h6v2 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Denial of Service in @commercial/hapi

Published

Sep 3, 2020

Updated

Aug 31, 2020

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

Exploitation data as of Aug 31, 2020 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

4 pkgs affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

2other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

@commercial/hapinpm

21downloads / week

Description

Affected versions of @commercial/hapi are vulnerable to Denial of Service. The CORS request handler has a vulnerability which will cause the function to throw a system error if the header contains some invalid values. If no unhandled exception handler is available, the application will exist, allowing an attacker to shut down services.

Recommendation

Upgrade to versions 16.8.2, 17.9.2, 18.4.1, 19.1.1 or later.

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@commercial/hapi`	all versions	16.8.2
📦npm	`@commercial/hapi`	≥ 17.0.0&&< 17.9.2	17.9.2
📦npm	`@commercial/hapi`	≥ 18.0.0&&< 18.4.1	18.4.1
📦npm	`@commercial/hapi`	≥ 19.0.0&&< 19.1.1	19.1.1

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @commercial/hapi. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update @commercial/hapi to 16.8.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-66mv-xh68-h6v2 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-66mv-xh68-h6v2 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-66mv-xh68-h6v2. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Affected versions of `@commercial/hapi` are vulnerable to Denial of Service. The CORS request handler has a vulnerability which will cause the function to throw a system error if the header contains some invalid values. If no unhandled exception handler is available, the application will exist, allowing an attacker to shut down services. ## Recommendation Upgrade to versions 16.8.2, 17.9.2, 18.4.1, 19.1.1 or later.

O3 Security · Impact-Aware SCA

Is GHSA-66mv-xh68-h6v2 in your dependencies?

O3 detects GHSA-66mv-xh68-h6v2 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works