Denial of Service in @commercial/ammo
Priority LOW 38Published · Updated
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- —
- Confidentiality · integrity · availability
- —
- Fix status
- Fixed
No CVSS vector from any source. Fix status from GitHub.
Summary
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.
Why it matters now
Fix Fixed @commercial/ammo (npm): 2.1.1
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | @commercial/ammo (npm) | before 2.1.1 | 2.1.1 | Patch available | GHSA-rhc3-76jw-4f2x |
- @commercial/ammo (npm) Vendor— Affected before 2.1.1 Fixed in 2.1.1 Patch available GHSA-rhc3-76jw-4f2x
Remediation
- Fix · GHSA-rhc3-76jw-4f2x @commercial/ammo (npm) Fixed in 2.1.1 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-rhc3-76jw-4f2x
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences