How severe is GHSA-gjph-xf5q-6mfq?

No CVSS score has been assigned to GHSA-gjph-xf5q-6mfq yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-gjph-xf5q-6mfq?

GHSA-gjph-xf5q-6mfq affects the following packages: @hapi/ammo (npm), @hapi/ammo (npm). Ecosystems affected: npm.

How do I fix GHSA-gjph-xf5q-6mfq?

Update @hapi/ammo to 3.1.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-gjph-xf5q-6mfq is resolved across your whole dependency graph.

How do I detect GHSA-gjph-xf5q-6mfq in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @hapi/ammo. 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-gjph-xf5q-6mfq 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-gjph-xf5q-6mfq?

O3 pinpoints whether GHSA-gjph-xf5q-6mfq 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-gjph-xf5q-6mfq actively exploited in the wild?

No public exploit code has been indexed for GHSA-gjph-xf5q-6mfq 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-gjph-xf5q-6mfq published, and has it been updated?

GHSA-gjph-xf5q-6mfq 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-gjph-xf5q-6mfq

GHSA-gjph-xf5q-6mfq is a security vulnerability in @hapi/ammo. O3 Security confirms whether GHSA-gjph-xf5q-6mfq is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Denial of Service in @hapi/ammo

Published

Sep 3, 2020

Updated

Aug 31, 2020

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

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

Real-World Exposure

2 pkgs affected

📦@hapi/ammo📦@hapi/ammo

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.

Description

Versions of @hapi/ammo prior to 3.1.2 or 5.0.1 are vulnerable to Denial of Service. The Range HTTP header parser has a vulnerability which will cause the function to throw a system error if the header is set to an invalid value. Because hapi is not expecting the function to ever throw, the error is thrown all the way up the stack. If no unhandled exception handler is available, the application will exist, allowing an attacker to shut down services.

Recommendation

Upgrade to version 3.1.2 or 5.0.1.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@hapi/ammo`	all versions	3.1.2
📦npm	`@hapi/ammo`	≥ 4.0.0&&< 5.0.1	5.0.1

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @hapi/ammo. 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 @hapi/ammo to 3.1.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-gjph-xf5q-6mfq 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-gjph-xf5q-6mfq 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-gjph-xf5q-6mfq. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Versions of `@hapi/ammo` prior to 3.1.2 or 5.0.1 are vulnerable to Denial of Service. The Range HTTP header parser has a vulnerability which will cause the function to throw a system error if the header is set to an invalid value. Because hapi is not expecting the function to ever throw, the error is thrown all the way up the stack. If no unhandled exception handler is available, the application will exist, allowing an attacker to shut down services. ## Recommendation Upgrade to version 3.1.2 or 5.0.1.

O3 Security · Impact-Aware SCA

Is GHSA-gjph-xf5q-6mfq in your dependencies?

O3 detects GHSA-gjph-xf5q-6mfq 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