Persisted Cross-Site Scripting in Frontend Rendering in typo3
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 8.7.51, 9.5.40, 10.4.36, 12.2.0, 11.5.23, and 1 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: poc
- Automatable: no
- Technical impact: partial
Summary
TYPO3 is a free and open source Content Management Framework released under the GNU General Public License. In affected versions the TYPO3 core component `GeneralUtility::getIndpEnv()` uses the unfiltered server environment variable `PATH_INFO`, which allows attackers to inject malicious content. In combination with the TypoScript setting `config.absRefPrefix=auto`, attackers can inject malicious HTML code to pages that have not been rendered and cached, yet. As a result, injected values would be cached and delivered to other website visitors (persisted cross-site scripting). Individual code which relies on the resolved value of `GeneralUtility::getIndpEnv('SCRIPT_NAME')` and corresponding usages (as shown below) are vulnerable as well. Additional investigations confirmed that at least Apache web server deployments using CGI (FPM, FCGI/FastCGI, and similar) are affected. However, there still might be the risk that other scenarios like nginx, IIS, or Apache/mod_php are vulnerable. The usage of server environment variable `PATH_INFO` has been removed from corresponding processings in `GeneralUtility::getIndpEnv()`. Besides that, the public property `TypoScriptFrontendController::$absRefPrefix` is encoded for both being used as a URI component and for being used as a prefix in an HTML context. This mitigates the cross-site scripting vulnerability. Users are advised to update to TYPO3 versions 8.7.51 ELTS, 9.5.40 ELTS, 10.4.35 LTS, 11.5.23 LTS and 12.2.0 which fix this problem. For users who are unable to patch in a timely manner the TypoScript setting `config.absRefPrefix` should at least be set to a static path value, instead of using auto - e.g. `config.absRefPrefix=/`. This workaround does not fix all aspects of the vulnerability, and is just considered to be an intermediate mitigation to the most prominent manifestation.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: poc · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- TYPO3 typo3
From 8.7.0 · fixed in 8.7.51; From 9.0.0 · fixed in 9.5.40; From 10.0.0 · fixed in 10.4.36; From 12.0.0 · fixed in 12.2.0
- typo3/cms-corePackagist
From 12.0.0 · fixed in 12.2.0
- typo3/cms-corePackagist
From 11.0.0 · fixed in 11.5.23
- typo3/cms-corePackagist
From 10.0.0 · fixed in 10.4.36
- typo3/cms-corePackagist
From 9.0.0 · fixed in 9.5.40
- typo3/cms-corePackagist
From 8.7.0 · fixed in 8.7.51
- typo3/cmsPackagist
From 10.0.0 · fixed in 10.4.35
- typo3/cmsPackagist
From 11.0.0 · fixed in 11.5.23
- typo3/cmsPackagist
From 12.0.0 · fixed in 12.2.0