# GHSA-jqr8-q455-xx45: TYPO3 Brute Force Protection Bypass in backend login

> Attackers can bypass backend login brute force protection by forging requests, facilitating credential guessing against editor accounts.

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

## What is GHSA-jqr8-q455-xx45?

GHSA-jqr8-q455-xx45 is a vulnerability in typo3/cms, published on 30 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The backend login has a basic brute force protection implementation which pauses for 5 seconds if wrong credentials are given. This pause however could be bypassed by forging a special request, making brute force attacks on backend editor credentials more feasible.

## Which versions are affected by GHSA-jqr8-q455-xx45?

4 open source packages ship an affected version, including typo3/cms.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `typo3/cms` | Packagist | From 6.2.0 | 6.2.14 |
| `typo3/cms` | Packagist | From 6.2.0 | 6.2.14 |
| `typo3/cms` | Packagist | From 7.0.0 | 7.3.1 |
| `typo3/cms` | Packagist | From 7.0.0 | 7.3.1 |

## How do I fix GHSA-jqr8-q455-xx45?

Upgrade typo3/cms to a fixed version for your release line: 6.2.14 or 7.3.1.

## Is GHSA-jqr8-q455-xx45 being exploited?

There is no known exploitation of GHSA-jqr8-q455-xx45 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-jqr8-q455-xx45 and fix it if it is affected.

What it is: GHSA-jqr8-q455-xx45 is a vulnerability in typo3/cms, published on 30 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-jqr8-q455-xx45 in the wild and no public exploit code.

Affected packages and fixed versions:
- typo3/cms (Packagist): affected from 6.2.0; fixed in 6.2.14
- typo3/cms (Packagist): affected from 6.2.0; fixed in 6.2.14
- typo3/cms (Packagist): affected from 7.0.0; fixed in 7.3.1
- typo3/cms (Packagist): affected from 7.0.0; fixed in 7.3.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-jqr8-q455-xx45/ (Markdown: https://insights.sbomify.com/GHSA-jqr8-q455-xx45/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-jqr8-q455-xx45

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