# GHSA-5854-jvxx-2cg9: Denial of Service in content

> An attacker can crash the application by sending a malformed Content-Encoding header, causing a denial of service.

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

## What is GHSA-5854-jvxx-2cg9?

GHSA-5854-jvxx-2cg9 is a denial of service vulnerability in content, published on 3 Sep 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Versions of `content` are vulnerable to Denial of Service. The Content-Encoding HTTP header parser has a vulnerability which will cause the function to throw a system error if the header contains some invalid values. Because hapi rethrows system errors (as opposed to catching expected application errors), 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

This package is deprecated and is now maintained as `@hapi/content`. Please update your dependencies to use `@hapi/content`.

## Which versions are affected by GHSA-5854-jvxx-2cg9?

2 open source packages ship an affected version, including content.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `content` | npm | All versions to 4.0.6 | None |
| `content` | npm | All versions to 4.0.6 | None |

## How do I fix GHSA-5854-jvxx-2cg9?

No fix has been published for GHSA-5854-jvxx-2cg9 yet. Limit exposure of the affected software until one is available.

## Is GHSA-5854-jvxx-2cg9 being exploited?

There is no known exploitation of GHSA-5854-jvxx-2cg9 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-5854-jvxx-2cg9 and fix it if it is affected.

What it is: GHSA-5854-jvxx-2cg9 is a denial of service vulnerability in content, published on 3 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-5854-jvxx-2cg9 in the wild and no public exploit code.

Affected packages and fixed versions:
- content (npm): affected all versions up to 4.0.6; no fix listed
- content (npm): affected all versions up to 4.0.6; no fix listed

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-5854-jvxx-2cg9/ (Markdown: https://insights.sbomify.com/GHSA-5854-jvxx-2cg9/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-5854-jvxx-2cg9

---
From sbomify Insights: https://insights.sbomify.com/GHSA-5854-jvxx-2cg9/
Summaries are generated and may contain mistakes; the official description above is the record.