# GHSA-cwgq-83w5-8jfq: silverstripe/framework has possible denial of service attack vector when flushing

> An unauthenticated attacker can trigger a denial of service via the dev/build system controller in SilverStripe framework.

- **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:** 28 May 2024

## What is GHSA-cwgq-83w5-8jfq?

GHSA-cwgq-83w5-8jfq is a denial of service vulnerability in silverstripe/framework, published on 28 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A possible denial of service attack vector has been identified in the dev/build system controller.

dev/build now has its own URL token, similar to flushtoken, to ensure users are authenticated when running dev/build outside of dev environments.

## Which versions are affected by GHSA-cwgq-83w5-8jfq?

6 open source packages ship an affected version, including silverstripe/framework.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `silverstripe/framework` | Packagist | From 4.0.0-rc1 | 4.0.5 |
| `silverstripe/framework` | Packagist | From 4.0.0-rc1 | 4.0.5 |
| `silverstripe/framework` | Packagist | From 4.1.0-rc1 | 4.1.3 |
| `silverstripe/framework` | Packagist | From 4.1.0-rc1 | 4.1.3 |
| `silverstripe/framework` | Packagist | From 4.2.0-rc1 | 4.2.2 |
| `silverstripe/framework` | Packagist | From 4.2.0-rc1 | 4.2.2 |

## How do I fix GHSA-cwgq-83w5-8jfq?

Upgrade silverstripe/framework to a fixed version for your release line: 4.0.5, 4.1.3 or 4.2.2.

## Is GHSA-cwgq-83w5-8jfq being exploited?

There is no known exploitation of GHSA-cwgq-83w5-8jfq in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-cwgq-83w5-8jfq and fix it if it is affected.

What it is: GHSA-cwgq-83w5-8jfq is a denial of service vulnerability in silverstripe/framework, published on 28 May 2024. 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-cwgq-83w5-8jfq in the wild and no public exploit code.

Affected packages and fixed versions:
- silverstripe/framework (Packagist): affected from 4.0.0-rc1; fixed in 4.0.5
- silverstripe/framework (Packagist): affected from 4.0.0-rc1; fixed in 4.0.5
- silverstripe/framework (Packagist): affected from 4.1.0-rc1; fixed in 4.1.3
- silverstripe/framework (Packagist): affected from 4.1.0-rc1; fixed in 4.1.3
- silverstripe/framework (Packagist): affected from 4.2.0-rc1; fixed in 4.2.2
- silverstripe/framework (Packagist): affected from 4.2.0-rc1; fixed in 4.2.2

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-cwgq-83w5-8jfq/ (Markdown: https://insights.sbomify.com/GHSA-cwgq-83w5-8jfq/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-cwgq-83w5-8jfq

---
From sbomify Insights: https://insights.sbomify.com/GHSA-cwgq-83w5-8jfq/
Summaries are generated and may contain mistakes; the official description above is the record.