Vulnerability advisory

CVE-2021-41114

Published Updated OSV record ↗

Also known as BIT-typo3-2021-41114GHSA-m2jh-fxw4-gphm

Severity
  • CVSS 3.xCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Affected versions

Repository

Affected commitsFixed by commit
GIT github.com/TYPO3/typo3 ↗
6a5e2d4097ef0a0e3ea955af93cf83810d6fa234 to before 0da4bf2966784c088931dbe7f8b23bb981bf00650da4bf2966784c088931dbe7f8b23bb981bf0065
Also listed as affected (5)
  • v11.4.0
  • v11.3.0
  • v11.2.0
  • v11.1.0
  • v11.0.0
GIT github.com/typo3/typo3 ↗
6a5e2d4097ef0a0e3ea955af93cf83810d6fa234 to before 0da4bf2966784c088931dbe7f8b23bb981bf00650da4bf2966784c088931dbe7f8b23bb981bf0065
Not specified5cbff85506cebe343e5ae59228977547cf8e3cf4
Also listed as affected (5)
  • v11.4.0
  • v11.3.0
  • v11.2.0
  • v11.1.0
  • v11.0.0

Description

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.

References

  • Codex
  • Claude Code
  • VS Code
  • GitHub Copilot
  • Cursor
  • Cline
  • Windsurf
  • Google Anti-gravity
  • OpenCode
  • Pi
  • Gemini CLI
  • Hermes Agent
  • Zed
  • Junie
  • Qwen Code
  • Kiro
  • Kilo Code
  • Factory Droid

Set up GitHits for your agents

Run this command:

<> bash
npx githits@latest init

What happens next:

  1. Opens your browser to authorize GitHits
  2. Asks whether to set up GitHits at the user or project level
  3. Detects your supported AI coding tools
  4. Lets you choose which tools to configure
  5. Configures the selected tools