# GHSA-hjx5-v9xg-7h25: TYPO3 Denial of Service in Frontend Record Registration

> Attackers can cause denial of service by creating arbitrary session records via unvalidated anonymous user sessions in TYPO3's record registration feature.

- **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-hjx5-v9xg-7h25?

GHSA-hjx5-v9xg-7h25 is a denial of service vulnerability in typo3/cms-core, published on 30 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

TYPO3’s built-in record registration functionality (aka “basic shopping cart”) using recs URL parameters is vulnerable to denial of service. Failing to properly ensure that anonymous user sessions are valid, attackers can use this vulnerability in order to create  an arbitrary amount of individual session-data records in the database.

## Which versions are affected by GHSA-hjx5-v9xg-7h25?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `typo3/cms-core` | Packagist | From 7.0.0 | 7.6.32 |
| `typo3/cms-core` | Packagist | From 7.0.0 | 7.6.32 |
| `typo3/cms-core` | Packagist | From 8.0.0 | 8.7.21 |
| `typo3/cms-core` | Packagist | From 8.0.0 | 8.7.21 |

## How do I fix GHSA-hjx5-v9xg-7h25?

Upgrade typo3/cms-core to a fixed version for your release line: 7.6.32 or 8.7.21.

## Is GHSA-hjx5-v9xg-7h25 being exploited?

There is no known exploitation of GHSA-hjx5-v9xg-7h25 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-hjx5-v9xg-7h25 and fix it if it is affected.

What it is: GHSA-hjx5-v9xg-7h25 is a denial of service vulnerability in typo3/cms-core, 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-hjx5-v9xg-7h25 in the wild and no public exploit code.

Affected packages and fixed versions:
- typo3/cms-core (Packagist): affected from 7.0.0; fixed in 7.6.32
- typo3/cms-core (Packagist): affected from 7.0.0; fixed in 7.6.32
- typo3/cms-core (Packagist): affected from 8.0.0; fixed in 8.7.21
- typo3/cms-core (Packagist): affected from 8.0.0; fixed in 8.7.21

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-hjx5-v9xg-7h25/ (Markdown: https://insights.sbomify.com/GHSA-hjx5-v9xg-7h25/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-hjx5-v9xg-7h25

---
From sbomify Insights: https://insights.sbomify.com/GHSA-hjx5-v9xg-7h25/
Summaries are generated and may contain mistakes; the official description above is the record.