Typo3 Vulnerable to Cache Poisoning
Impact
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…
Source excerpt · OSVAffected packages
Start with the recorded fix for your release branch. Check your installed version and test compatibility before upgrading. Fixing this advisory does not rule out other vulnerabilities in the release.
| Affected range | Recorded fix |
|---|---|
| From 4.5.0 before 4.5.39Ecosystem versions | 4.5.39 |
| From 6.2.0 before 6.2.9Ecosystem versions | 6.2.9 |
| From 7.0.0 before 7.0.2Ecosystem versions | 7.0.2 |
| From 4.6.0 before 4.6.19Ecosystem versions | 4.6.19 |
| From 4.7.0 before 4.7.21Ecosystem versions | 4.7.21 |
| From 6.0.0 before 6.0.15Ecosystem versions | 6.0.15 |
| From 6.1.0 before 6.1.13Ecosystem versions | 6.1.13 |
Version evidence: OSV · GHSA-5479-gqqr-f9gj
View original version evidence (11 explicit versions)
Original source description
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.