How severe is GHSA-rhc3-76jw-4f2x?

No CVSS score has been assigned to GHSA-rhc3-76jw-4f2x yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-rhc3-76jw-4f2x?

GHSA-rhc3-76jw-4f2x affects the following packages: @commercial/ammo (npm). Ecosystems affected: npm.

How do I fix GHSA-rhc3-76jw-4f2x?

Update @commercial/ammo to 2.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rhc3-76jw-4f2x is resolved across your whole dependency graph.

How do I detect GHSA-rhc3-76jw-4f2x in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @commercial/ammo, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-rhc3-76jw-4f2x if there is no patch (or I can't update yet)?

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is GHSA-rhc3-76jw-4f2x actively exploited in the wild?

No public exploit code has been indexed for GHSA-rhc3-76jw-4f2x 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-rhc3-76jw-4f2x published, and has it been updated?

GHSA-rhc3-76jw-4f2x was published on September 4, 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

Denial of Service in @commercial/ammoGHSA-rhc3-76jw-4f2x

GHSA-rhc3-76jw-4f2x is a security vulnerability in @commercial/ammo. A fix is available for @commercial/ammo — see the affected versions and patch details below.

Published

Sep 4, 2020

Updated

Aug 31, 2020

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

Real-World Exposure

1 pkg 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.

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

@commercial/ammonpm

20downloads / week

Description

Versions of @commercial/ammo prior to 2.1.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 2.1.1 or later.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@commercial/ammo`	all versions	2.1.1`npm install @commercial/ammo@2.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/ammo, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @commercial/ammo to 2.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rhc3-76jw-4f2x is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Frequently Asked Questions

Versions of `@commercial/ammo` prior to 2.1.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 2.1.1 or later.

O3 Security · Impact-Aware SCA

Is GHSA-rhc3-76jw-4f2x in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works