Typo3 Vulnerable to Cache Poisoning
Published 17 May 2022 · Updated 29 Nov 2024
Affected packages
- Affected
- >=4.5.0 <4.5.39
- Fixed in
- 4.5.39
composer require typo3/cms:^4.5.39- Affected
- >=6.2.0 <6.2.9
- Fixed in
- 6.2.9
composer require typo3/cms:^6.2.9- Affected
- >=7.0.0 <7.0.2
- Fixed in
- 7.0.2
composer require typo3/cms:^7.0.2- Affected
- >=4.6.0 <4.6.19
- Fixed in
- 4.6.19
composer require typo3/cms:^4.6.19- Affected
- >=4.7.0 <4.7.21
- Fixed in
- 4.7.21
composer require typo3/cms:^4.7.21- Affected
- >=6.0.0 <6.0.15
- Fixed in
- 6.0.15
composer require typo3/cms:^6.0.15- Affected
- >=6.1.0 <6.1.13
- Fixed in
- 6.1.13
composer require typo3/cms:^6.1.13Details
Problem Description: A request URL with arbitrary arguments, but still pointing to the home page of a TYPO3 installation can be cached if the configuration option config.prefixLocalAnchors is used with the values "all" or "cached". The impact of this vulnerability is that unfamiliar looking links to the home page can end up in the cache, which leads to a reload of the page in the browser when section links are followed by web page visitors, instead of just directly jumping to the requested section of the page. TYPO3 versions 4.6.x and higher are only affected if the homepage is not a shortcut to a different page.
Solution: Removing the configuration options config.prefixLocalAnchors (and optionally also config.baseUrl) in favor of config.absRefPrefix
Credits: Thanks to Gernot Leitgab who discovered and reported the vulnerability.
Is GHSA-5479-gqqr-f9gj 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.