Summary
Typo3 Vulnerable to Cache Poisoning
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.
Impact
The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths. Typical impact: varies by context: data corruption, logic bypass, or denial of service.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
typo3/cms to 4.5.39 or later; typo3/cms to 6.2.9 or later; typo3/cms to 7.0.2 or later; typo3/cms to 4.6.19 or later; typo3/cms to 4.7.21 or later; typo3/cms to 6.0.15 or later; typo3/cms to 6.1.13 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2014-9509? CVE-2014-9509 is a high-severity improper input validation vulnerability in typo3/cms (composer), affecting versions >= 4.5.0, < 4.5.39. It is fixed in 4.5.39, 6.2.9, 7.0.2, 4.6.19, 4.7.21, 6.0.15, 6.1.13. The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths.
- Which versions of typo3/cms are affected by CVE-2014-9509? typo3/cms (composer) versions >= 4.5.0, < 4.5.39 is affected.
- Is there a fix for CVE-2014-9509? Yes. CVE-2014-9509 is fixed in 4.5.39, 6.2.9, 7.0.2, 4.6.19, 4.7.21, 6.0.15, 6.1.13. Upgrade to this version or later.
- Is CVE-2014-9509 exploitable, and should I be worried? Whether CVE-2014-9509 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2014-9509 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2014-9509?
- Upgrade
typo3/cmsto 4.5.39 or later - Upgrade
typo3/cmsto 6.2.9 or later - Upgrade
typo3/cmsto 7.0.2 or later - Upgrade
typo3/cmsto 4.6.19 or later - Upgrade
typo3/cmsto 4.7.21 or later - Upgrade
typo3/cmsto 6.0.15 or later - Upgrade
typo3/cmsto 6.1.13 or later
- Upgrade