Cache Flooding in TYPO3 Frontend
Links with a valid cHash argument lead to newly generated page cache entries. Because the cHash is not bound to a specific page, attackers could use valid cHash arguments for multiple pages, leading to additional useless page cache entries. Depending on the number of pages in the system and the number of available valid links with a cHash, attackers could add a considerable amount of additional cache entries, which in the end exceed storage limits and thus could lead to the system not responding any more. This means the Cache Flooding attack potentially could lead to a successful Denial of Service (DoS) attack.
Affected software
Click a technology to see all vulnerabilities affecting it.
| Platform | Package | Vulnerable versions | Fixed in |
|---|---|---|---|
| Composer package | typo3/cms | >= 6.2.0, < 6.2.27, >= 7.6.0, < 7.6.11, >= 8.0.0, < 8.3.1 | 6.2.27, 7.6.11, 8.3.1 |
References
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L- Weakness (CWE)
-- Platform
- Composer
- Package
typo3/cms- Disclosed
- 05.06.2024
- Updated
- 11.10.2026 10:22
Sources and licenses
OSV / GitHub Advisory Database - GHSA-pw2q-qwvj-gh43 - CC BY 4.0
Vulnerability history: typo3/cms
All published vulnerabilities of this package (Composer package), newest first. Shows whether this is a one-off slip or a package that needs watching.
- Total entries
- 188
- First → latest
- 09.2018 06.2024
- Without a fix
- 3
- Exploited in attacks
- 0
Severity breakdown
- Critical 6
- High 41
- Medium 128
- Low 13
Disclosures per year
- 2018: 2
- 2019: 0
- 2020: 13
- 2021: 15
- 2022: 85
- 2023: 1
- 2024: 72
- 2025: 0
- 2026: 0
-
Cache Flooding in TYPO3 Frontend this entry
Know which vulnerabilities affect your application
With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.