# GHSA-rhc3-76jw-4f2x: Denial of Service in @commercial/ammo

> An attacker can crash the application by sending a malformed Range HTTP header, causing an unhandled exception in the @commercial/ammo library.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 4 Sep 2020

## What is GHSA-rhc3-76jw-4f2x?

GHSA-rhc3-76jw-4f2x is a denial of service vulnerability in @commercial/ammo, published on 4 Sep 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

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

2 open source packages ship an affected version, including @commercial/ammo.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@commercial/ammo` | npm | All versions | 2.1.1 |
| `@commercial/ammo` | npm | All versions | 2.1.1 |

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

Upgrade @commercial/ammo to 2.1.1 or later.

## Is GHSA-rhc3-76jw-4f2x being exploited?

There is no known exploitation of GHSA-rhc3-76jw-4f2x in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-rhc3-76jw-4f2x and fix it if it is affected.

What it is: GHSA-rhc3-76jw-4f2x is a denial of service vulnerability in @commercial/ammo, published on 4 Sep 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-rhc3-76jw-4f2x in the wild and no public exploit code.

Affected packages and fixed versions:
- @commercial/ammo (npm): affected all versions; fixed in 2.1.1
- @commercial/ammo (npm): affected all versions; fixed in 2.1.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-rhc3-76jw-4f2x/ (Markdown: https://insights.sbomify.com/GHSA-rhc3-76jw-4f2x/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-rhc3-76jw-4f2x

---
From sbomify Insights: https://insights.sbomify.com/GHSA-rhc3-76jw-4f2x/
Summaries are generated and may contain mistakes; the official description above is the record.