# GHSA-2mvq-xp48-4c77: Denial of Service in subtext

> Attackers can cause Denial of Service by sending large chunked payloads that bypass maxBytes limits, exhausting system resources.

- **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-2mvq-xp48-4c77?

GHSA-2mvq-xp48-4c77 is a denial of service vulnerability in subtext, published on 3 Sep 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

All versions of `subtext` are vulnerable to Denial of Service (DoS). The package fails to enforce the `maxBytes` configuration for payloads with chunked encoding that are written to the file system. This allows attackers to send requests with arbitrary payload sizes, which may exhaust system resources leading to Denial of Service.

## Recommendation

This package is not actively maintained and has been moved to `@hapi/subtext` where version 6.1.2.

## Which versions are affected by GHSA-2mvq-xp48-4c77?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `subtext` | npm | From 0.0.0 | None |
| `subtext` | npm | From 0.0.0 | None |

## How do I fix GHSA-2mvq-xp48-4c77?

No fix has been published for GHSA-2mvq-xp48-4c77 yet. Limit exposure of the affected software until one is available.

## Is GHSA-2mvq-xp48-4c77 being exploited?

There is no known exploitation of GHSA-2mvq-xp48-4c77 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-2mvq-xp48-4c77 and fix it if it is affected.

What it is: GHSA-2mvq-xp48-4c77 is a denial of service vulnerability in subtext, 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-2mvq-xp48-4c77 in the wild and no public exploit code.

Affected packages and fixed versions:
- subtext (npm): affected from 0.0.0; no fix listed
- subtext (npm): affected from 0.0.0; 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-2mvq-xp48-4c77/ (Markdown: https://insights.sbomify.com/GHSA-2mvq-xp48-4c77/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-2mvq-xp48-4c77

---
From sbomify Insights: https://insights.sbomify.com/GHSA-2mvq-xp48-4c77/
Summaries are generated and may contain mistakes; the official description above is the record.