HTTP Host Header Injection in Request Handling in Typo3
typo3
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| typo3/cms-core Packagist |
|
|
| typo3/cms Packagist |
|
|
typo3
| Product | Affected | Fixed in |
|---|---|---|
| typo3/cms-core Packagist |
|
|
| typo3/cms Packagist |
|
|
TYPO3 is an open source PHP based web content management system released under the GNU GPL. It has been discovered that TYPO3 CMS is susceptible to host spoofing due to improper validation of the HTTP Host header. TYPO3 uses the HTTP Host header, for example, to generate absolute URLs during the frontend rendering process. Since the host header itself is provided by the client, it can be forged to any value, even in a name-based virtual hosts environment. This vulnerability is the same as described in TYPO3-CORE-SA-2014-001 (CVE-2014-3941). A regression, introduced during TYPO3 v11 development, led to this situation. The already existing setting $GLOBALS['TYPO3_CONF_VARS']['SYS']['trustedHostsPattern'] (used as an effective mitigation strategy in previous TYPO3 versions) was not evaluated anymore, and reintroduced the vulnerability.
From the CVE record · GitHub_M
TYPO3 CMS improperly validates the client-supplied HTTP Host header, allowing an attacker to spoof the host used to generate absolute URLs during frontend rendering. The regression affects TYPO3 v11 releases before 11.5.0, where the existing trustedHostsPattern setting is no longer evaluated.
Teams running Packagist packages typo3/cms-core or typo3/cms at versions >=11.0.0 and <11.5.0 should check their deployments.