# GHSA-8v6m-7f5v-hhx6: Silverstripe Brute force bypass on default admin

> Attackers can bypass brute force protections on default admin accounts in Silverstripe, enabling unlimited login attempts and potential account takeover.

- **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-8v6m-7f5v-hhx6?

GHSA-8v6m-7f5v-hhx6 is a 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

Default Administrator accounts were not subject to the same brute force protection afforded to other Member accounts. Failed login counts were not logged for default admins resulting in unlimited attempts on the default admin username and password.

## Which versions are affected by GHSA-8v6m-7f5v-hhx6?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `silverstripe/framework` | Packagist | From 3.1.18 | 3.1.19 |
| `silverstripe/framework` | Packagist | From 3.1.18 | 3.1.19 |
| `silverstripe/framework` | Packagist | From 3.2.3 | 3.2.4 |
| `silverstripe/framework` | Packagist | From 3.2.3 | 3.2.4 |
| `silverstripe/framework` | Packagist | From 3.3.1 | 3.3.2 |
| `silverstripe/framework` | Packagist | From 3.3.1 | 3.3.2 |

## How do I fix GHSA-8v6m-7f5v-hhx6?

Upgrade silverstripe/framework to a fixed version for your release line: 3.1.19, 3.2.4 or 3.3.2.

## Is GHSA-8v6m-7f5v-hhx6 being exploited?

There is no known exploitation of GHSA-8v6m-7f5v-hhx6 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-8v6m-7f5v-hhx6 and fix it if it is affected.

What it is: GHSA-8v6m-7f5v-hhx6 is a 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-8v6m-7f5v-hhx6 in the wild and no public exploit code.

Affected packages and fixed versions:
- silverstripe/framework (Packagist): affected from 3.1.18; fixed in 3.1.19
- silverstripe/framework (Packagist): affected from 3.1.18; fixed in 3.1.19
- silverstripe/framework (Packagist): affected from 3.2.3; fixed in 3.2.4
- silverstripe/framework (Packagist): affected from 3.2.3; fixed in 3.2.4
- silverstripe/framework (Packagist): affected from 3.3.1; fixed in 3.3.2
- silverstripe/framework (Packagist): affected from 3.3.1; fixed in 3.3.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-8v6m-7f5v-hhx6/ (Markdown: https://insights.sbomify.com/GHSA-8v6m-7f5v-hhx6/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-8v6m-7f5v-hhx6

---
From sbomify Insights: https://insights.sbomify.com/GHSA-8v6m-7f5v-hhx6/
Summaries are generated and may contain mistakes; the official description above is the record.