GIVE YOUR AGENT THE EVIDENCE

Set up in your agent.

One prompt to get started. Paste it into your coding agent to connect cve.new through MCP and bring vulnerability context into your workflow.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

GIVE YOUR AGENT THE EVIDENCE

Investigate in your agent.

Turn this advisory into a focused investigation. Ask your agent to check your project’s versions, explain the evidence, and suggest a compatible fix.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

cve.new
GHSA-m2jh-fxw4-gphmmedium4.8

HTTP Host Header Injection

Check your stack

The advisory, in context

Meta

  • CVSS: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N/E:F/RL:O/RC:C (3.5)

Problem

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.

Solution

Update your instance to TYPO3 version 11.5.0 which addresses the problem described.

Credits

Thanks to TYPO3 framework merger Benjamin Franzke who reported and fixed the issue.

References

Affected 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.

Ecosystem versions

From 11.0.0 before 11.5.0

Fixed in 11.5.0

9 explicitly affected versions

v11.0.0, v11.1.0, v11.1.1, v11.2.0, v11.3.0, v11.3.1, v11.3.2, v11.3.3, v11.4.0

View affected-version evidence
{
  "ranges": [
    {
      "events": [
        {
          "introduced": "11.0.0"
        },
        {
          "fixed": "11.5.0"
        }
      ],
      "type": "ECOSYSTEM"
    }
  ],
  "versions": [
    "v11.0.0",
    "v11.1.0",
    "v11.1.1",
    "v11.2.0",
    "v11.3.0",
    "v11.3.1",
    "v11.3.2",
    "v11.3.3",
    "v11.4.0"
  ]
}
typo3/cms Packagist
Ecosystem versions

From 11.0.0 before 11.5.0

Fixed in 11.5.0

9 explicitly affected versions

v11.0.0, v11.1.0, v11.1.1, v11.2.0, v11.3.0, v11.3.1, v11.3.2, v11.3.3, v11.4.0

View affected-version evidence
{
  "ranges": [
    {
      "events": [
        {
          "introduced": "11.0.0"
        },
        {
          "fixed": "11.5.0"
        }
      ],
      "type": "ECOSYSTEM"
    }
  ],
  "versions": [
    "v11.0.0",
    "v11.1.0",
    "v11.1.1",
    "v11.2.0",
    "v11.3.0",
    "v11.3.1",
    "v11.3.2",
    "v11.3.3",
    "v11.4.0"
  ]
}

References