# GHSA-g4hp-pfvf-vm5w: SilverStripe Vulnerability on 'isDev', 'isTest' and 'flush' $_GET validation

> Attackers can bypass authentication for development and flush modes by providing empty tokens, potentially causing denial of service or exposing debug information.

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

## What is GHSA-g4hp-pfvf-vm5w?

GHSA-g4hp-pfvf-vm5w is an authentication bypass vulnerability in silverstripe/framework, published on 23 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

When a secure token parameter is provided to a SilverStripe site (such as isDev or flush) an empty token parameter can be provided in order to bypass normal authentication parameters.

For instance, http://www.mysite.com/?isDev=1&isDevtoken will force a site to dev mode. Alternatively, "flush" could also be used in succession to cause excessive load on a victim site and risk denial of service.

The fix in this case is to ensure that empty tokens fail the validation check.

## Which versions are affected by GHSA-g4hp-pfvf-vm5w?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `silverstripe/framework` | Packagist | From 3.0.0 | 3.0.14 |
| `silverstripe/framework` | Packagist | From 3.0.0 | 3.0.14 |
| `silverstripe/framework` | Packagist | From 3.1.0 | 3.1.13 |
| `silverstripe/framework` | Packagist | From 3.1.0 | 3.1.13 |

## How do I fix GHSA-g4hp-pfvf-vm5w?

Upgrade silverstripe/framework to a fixed version for your release line: 3.0.14 or 3.1.13.

## Is GHSA-g4hp-pfvf-vm5w being exploited?

There is no known exploitation of GHSA-g4hp-pfvf-vm5w in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-g4hp-pfvf-vm5w and fix it if it is affected.

What it is: GHSA-g4hp-pfvf-vm5w is an authentication bypass vulnerability in silverstripe/framework, published on 23 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-g4hp-pfvf-vm5w in the wild and no public exploit code.

Affected packages and fixed versions:
- silverstripe/framework (Packagist): affected from 3.0.0; fixed in 3.0.14
- silverstripe/framework (Packagist): affected from 3.0.0; fixed in 3.0.14
- silverstripe/framework (Packagist): affected from 3.1.0; fixed in 3.1.13
- silverstripe/framework (Packagist): affected from 3.1.0; fixed in 3.1.13

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-g4hp-pfvf-vm5w/ (Markdown: https://insights.sbomify.com/GHSA-g4hp-pfvf-vm5w/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-g4hp-pfvf-vm5w

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