# GHSA-6f9m-v7mp-7jjq: Authentication Bypass in TYPO3 CMS

> Attackers can bypass authentication in TYPO3 CMS if MD5 hashing is configured, allowing unauthorized access to user 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:** 5 Jun 2024

## What is GHSA-6f9m-v7mp-7jjq?

GHSA-6f9m-v7mp-7jjq is an authentication bypass vulnerability in typo3/cms, published on 5 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

It has been discovered that TYPO3’s Salted Password system extension (which is a mandatory system component) is vulnerable to Authentication Bypass when using hashing methods which are related by PHP class inheritance. In standard TYPO3 core distributions stored passwords using the blowfish hashing algorithm can be overridden when using MD5 as the default hashing algorithm by just knowing a valid username. Per default the Portable PHP hashing algorithm (PHPass) is used which is not vulnerable.

## Which versions are affected by GHSA-6f9m-v7mp-7jjq?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `typo3/cms` | Packagist | From 7.0.0 | 7.6.30 |
| `typo3/cms` | Packagist | From 7.0.0 | 7.6.30 |
| `typo3/cms` | Packagist | From 8.0.0 | 8.7.17 |
| `typo3/cms` | Packagist | From 8.0.0 | 8.7.17 |
| `typo3/cms` | Packagist | From 9.0.0 | 9.3.2 |
| `typo3/cms` | Packagist | From 9.0.0 | 9.3.2 |

## How do I fix GHSA-6f9m-v7mp-7jjq?

Upgrade typo3/cms to a fixed version for your release line: 7.6.30, 8.7.17 or 9.3.2.

## Is GHSA-6f9m-v7mp-7jjq being exploited?

There is no known exploitation of GHSA-6f9m-v7mp-7jjq in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-6f9m-v7mp-7jjq and fix it if it is affected.

What it is: GHSA-6f9m-v7mp-7jjq is an authentication bypass vulnerability in typo3/cms, published on 5 Jun 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-6f9m-v7mp-7jjq in the wild and no public exploit code.

Affected packages and fixed versions:
- typo3/cms (Packagist): affected from 7.0.0; fixed in 7.6.30
- typo3/cms (Packagist): affected from 7.0.0; fixed in 7.6.30
- typo3/cms (Packagist): affected from 8.0.0; fixed in 8.7.17
- typo3/cms (Packagist): affected from 8.0.0; fixed in 8.7.17
- typo3/cms (Packagist): affected from 9.0.0; fixed in 9.3.2
- typo3/cms (Packagist): affected from 9.0.0; fixed in 9.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-6f9m-v7mp-7jjq/ (Markdown: https://insights.sbomify.com/GHSA-6f9m-v7mp-7jjq/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-6f9m-v7mp-7jjq

---
From sbomify Insights: https://insights.sbomify.com/GHSA-6f9m-v7mp-7jjq/
Summaries are generated and may contain mistakes; the official description above is the record.