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

GHSA-87pf-7x99-5xc4medium6.5

Silverstripe Hostname, IP and Protocol Spoofing through HTTP Headers

No CVE assignedCheck your stack

The advisory, in context

In it's default configuration, SilverStripe trusts all originating IPs to include HTTP headers for Hostname, IP and Protocol. This enables reverse proxies to forward requests while still retaining the original request information. Trusted IPs can be limited via the SS_TRUSTED_PROXY_IPS constant. Even with this restriction in place, SilverStripe trusts a variety of HTTP headers due to different proxy notations (e.g. X-Forwarded-For vs. Client-IP). Unless a proxy explicitly unsets invalid HTTP headers from connecting clients, this can lead to spoofing requests being passed through trusted proxies.

The impact of spoofed headers can include Director::forceSSL() not being enforced, SS_HTTPRequest->getIP() returning a wrong IP (disabling any IP restrictions), and spoofed hostnames circumventing any hostname-specific restrictions enforced in SilverStripe Controllers.

Regardless on running a reverse proxy in your hosting infrastructure, please follow the instructions on Secure Coding: Request hostname forgery in order to opt-in to these protections. If your website is not behind a reverse proxy, you might already be protected if using Apache with mod_env enabled, and you have the following line in your .htaccess file: SetEnv BlockUntrustedIPs true.

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

Earlier releases before 3.1.17

Fixed in 3.1.17

68 explicitly affected versions

2.4.10, 2.4.11, 2.4.12, 2.4.13, 2.4.9, 2.5.0, 3.0.10, 3.0.10-rc1, 3.0.11, 3.0.11-rc1, 3.0.12, 3.0.13, 3.0.14, 3.0.2.1, 3.0.3, 3.0.3-rc1, 3.0.3-rc2, 3.0.4, 3.0.5, 3.0.6, 3.0.6-rc1, 3.0.6-rc2, 3.0.7, 3.0.7-rc1, 3.0.8, 3.0.9, 3.0.9-rc1, 3.1.0, 3.1.0-beta1, 3.1.0-beta2, 3.1.0-beta3, 3.1.0-rc1, 3.1.0-rc2, 3.1.0-rc3, 3.1.1, 3.1.10, 3.1.10-rc1, 3.1.10-rc2, 3.1.11, 3.1.11-rc1, 3.1.12, 3.1.13, 3.1.13-rc1, 3.1.14, 3.1.14-rc1, 3.1.15, 3.1.16, 3.1.16-rc1, 3.1.17-rc1, 3.1.17-rc2, 3.1.2, 3.1.2-rc1, 3.1.3, 3.1.3-rc1, 3.1.3-rc2, 3.1.4, 3.1.4-rc1, 3.1.5, 3.1.5-rc1, 3.1.6, 3.1.6-rc1, 3.1.6-rc2, 3.1.6-rc3, 3.1.7, 3.1.7-rc1, 3.1.8, 3.1.9, 3.1.9-rc1

View affected-version evidence
{
  "ranges": [
    {
      "events": [
        {
          "introduced": "0"
        },
        {
          "fixed": "3.1.17"
        }
      ],
      "type": "ECOSYSTEM"
    }
  ],
  "versions": [
    "2.4.10",
    "2.4.11",
    "2.4.12",
    "2.4.13",
    "2.4.9",
    "2.5.0",
    "3.0.10",
    "3.0.10-rc1",
    "3.0.11",
    "3.0.11-rc1",
    "3.0.12",
    "3.0.13",
    "3.0.14",
    "3.0.2.1",
    "3.0.3",
    "3.0.3-rc1",
    "3.0.3-rc2",
    "3.0.4",
    "3.0.5",
    "3.0.6",
    "3.0.6-rc1",
    "3.0.6-rc2",
    "3.0.7",
    "3.0.7-rc1",
    "3.0.8",
    "3.0.9",
    "3.0.9-rc1",
    "3.1.0",
    "3.1.0-beta1",
    "3.1.0-beta2",
    "3.1.0-beta3",
    "3.1.0-rc1",
    "3.1.0-rc2",
    "3.1.0-rc3",
    "3.1.1",
    "3.1.10",
    "3.1.10-rc1",
    "3.1.10-rc2",
    "3.1.11",
    "3.1.11-rc1",
    "3.1.12",
    "3.1.13",
    "3.1.13-rc1",
    "3.1.14",
    "3.1.14-rc1",
    "3.1.15",
    "3.1.16",
    "3.1.16-rc1",
    "3.1.17-rc1",
    "3.1.17-rc2",
    "3.1.2",
    "3.1.2-rc1",
    "3.1.3",
    "3.1.3-rc1",
    "3.1.3-rc2",
    "3.1.4",
    "3.1.4-rc1",
    "3.1.5",
    "3.1.5-rc1",
    "3.1.6",
    "3.1.6-rc1",
    "3.1.6-rc2",
    "3.1.6-rc3",
    "3.1.7",
    "3.1.7-rc1",
    "3.1.8",
    "3.1.9",
    "3.1.9-rc1"
  ]
}
Ecosystem versions

From 3.2.0 before 3.2.2

Fixed in 3.2.2

6 explicitly affected versions

3.2.0, 3.2.1, 3.2.1-rc1, 3.2.1-rc2, 3.2.2-rc1, 3.2.2-rc2

View affected-version evidence
{
  "ranges": [
    {
      "events": [
        {
          "introduced": "3.2.0"
        },
        {
          "fixed": "3.2.2"
        }
      ],
      "type": "ECOSYSTEM"
    }
  ],
  "versions": [
    "3.2.0",
    "3.2.1",
    "3.2.1-rc1",
    "3.2.1-rc2",
    "3.2.2-rc1",
    "3.2.2-rc2"
  ]
}
Ecosystem versions

From 3.3.0-beta1 before 3.3.0

Fixed in 3.3.0

4 explicitly affected versions

3.3.0-beta1, 3.3.0-rc1, 3.3.0-rc2, 3.3.0-rc3

View affected-version evidence
{
  "ranges": [
    {
      "events": [
        {
          "introduced": "3.3.0-beta1"
        },
        {
          "fixed": "3.3.0"
        }
      ],
      "type": "ECOSYSTEM"
    }
  ],
  "versions": [
    "3.3.0-beta1",
    "3.3.0-rc1",
    "3.3.0-rc2",
    "3.3.0-rc3"
  ]
}

References