# GHSA-xm28-fw2x-fqv2: Denial of Service in foreman

> Attackers can cause a denial of service in Foreman by sending specially crafted requests with malicious paths.

- **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:** 31 May 2019

## What is GHSA-xm28-fw2x-fqv2?

GHSA-xm28-fw2x-fqv2 is a denial of service vulnerability in foreman, published on 31 May 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

All versions of `foreman` are vulnerable to Regular Expression Denial of Service when requests to it are made with a specially crafted path.

## Recommendation

Upgrade to version 3.0.1.

## Which versions are affected by GHSA-xm28-fw2x-fqv2?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `foreman` | npm | All versions | 3.0.1 |
| `foreman` | npm | All versions | 3.0.1 |

## How do I fix GHSA-xm28-fw2x-fqv2?

Upgrade foreman to 3.0.1 or later.

## Is GHSA-xm28-fw2x-fqv2 being exploited?

There is no known exploitation of GHSA-xm28-fw2x-fqv2 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-xm28-fw2x-fqv2 and fix it if it is affected.

What it is: GHSA-xm28-fw2x-fqv2 is a denial of service vulnerability in foreman, published on 31 May 2019. 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-xm28-fw2x-fqv2 in the wild and no public exploit code.

Affected packages and fixed versions:
- foreman (npm): affected all versions; fixed in 3.0.1
- foreman (npm): affected all versions; fixed in 3.0.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-xm28-fw2x-fqv2/ (Markdown: https://insights.sbomify.com/GHSA-xm28-fw2x-fqv2/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-xm28-fw2x-fqv2

---
From sbomify Insights: https://insights.sbomify.com/GHSA-xm28-fw2x-fqv2/
Summaries are generated and may contain mistakes; the official description above is the record.