Cache Flooding in TYPO3 Frontend
Published 5 Jun 2024 · Updated 2 Dec 2024
Affected packages
- Affected
- >=6.2.0 <6.2.27
- Fixed in
- 6.2.27
composer require typo3/cms:^6.2.27- Affected
- >=7.6.0 <7.6.11
- Fixed in
- 7.6.11
composer require typo3/cms:^7.6.11- Affected
- >=8.0.0 <8.3.1
- Fixed in
- 8.3.1
composer require typo3/cms:^8.3.1Details
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.
Is GHSA-pw2q-qwvj-gh43 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected typo3/cms, and gives you the command that fixes it.
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.