GHSA-87pf-7x99-5xc4: Silverstripe/framework Silverstripe Hostname, IP And Protocol Vulnerability

MODERATE
CVSS 6.5
Published
Advisory Summary

GHSA-87pf-7x99-5xc4 is a MODERATE (CVSS 6.5) silverstripe hostname, ip and protocol vulnerability (General Security Weakness) affecting Silverstripe/framework libraries in the Packagist ecosystem. The issue involves silverstripe hostname, ip and protocol spoofing through http headers. Remediation is available by upgrading affected packages to version 3.1.17, 3.2.2, 3.3.0.

GHSA-87pf-7x99-5xc4 at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-87pf-7x99-5xc4
Severity MODERATE
CVSS v3.1 Base Score 6.5
CWE Classification General Security Weakness
Affected Product Silverstripe/framework
Package Ecosystem Packagist
Published Date
Last Updated

Security Impact

CVSS: 6.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality Low (C:L)
Integrity Low (I:L)
Availability None (A:N)

How to Fix GHSA-87pf-7x99-5xc4

To remediate this vulnerability, upgrade all affected Silverstripe/framework dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

silverstripe/framework fixed: 3.1.17
Upgrade silverstripe/framework to 3.1.17
silverstripe/framework fixed: 3.2.2
Upgrade silverstripe/framework to 3.2.2
silverstripe/framework fixed: 3.3.0
Upgrade silverstripe/framework to 3.3.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for silverstripe/framework

How to Check if You Are Affected

To determine whether your application is affected by GHSA-87pf-7x99-5xc4, inspect your project dependencies for Silverstripe/framework:

inspect dependencies for silverstripe/framework

Analyze the terminal output to locate any version of Silverstripe/framework in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 3.1.17), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under General Security Weakness. In Silverstripe/framework, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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.

GHSA-87pf-7x99-5xc4 Affected Silverstripe/framework Versions

3 component(s)
Fixed Versions:
3.1.173.2.23.3.0
Product / Package Ecosystem Affected Versions Fixed Version
silverstripe/framework
Packagist
< 3.1.17
3.1.17
silverstripe/framework
Packagist
≥ 3.2.0
< 3.2.2
3.2.2
silverstripe/framework
Packagist
≥ 3.3.0-beta1
< 3.3.0
3.3.0

References

Frequently Asked Questions

What is GHSA-87pf-7x99-5xc4?
GHSA-87pf-7x99-5xc4 is a security vulnerability in Silverstripe/framework involving Silverstripe Hostname, IP and Protocol Spoofing through HTTP Headers under General Security Weakness.
Which Silverstripe/framework versions are affected?
Affected versions include releases prior to 3.1.17, 3.2.2, 3.3.0 across affected packages: silverstripe/framework.
What version fixes GHSA-87pf-7x99-5xc4?
Upgrading to 3.1.17, 3.2.2, 3.3.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is silverstripe/framework affected?
Yes, silverstripe/framework is affected in releases prior to 3.1.17, 3.2.2, 3.3.0. Upgrade your dependency to 3.1.17, 3.2.2, 3.3.0 or later.
What is the CVSS score of GHSA-87pf-7x99-5xc4?
GHSA-87pf-7x99-5xc4 has a CVSS v3.1 base score of 6.5 (MODERATE) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N.
What CWE is associated with GHSA-87pf-7x99-5xc4?
GHSA-87pf-7x99-5xc4 is classified under General Security Weakness.
How can I check Packagist dependencies for GHSA-87pf-7x99-5xc4?
Run the dependency tree command: 'inspect dependencies for silverstripe/framework'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-87pf-7x99-5xc4",
  "modified" : "2024-05-23T19:28:06Z",
  "published" : "2024-05-23T19:27:33Z",
  "aliases" : [ ],
  "summary" : "Silverstripe Hostname, IP and Protocol Spoofing through HTTP Headers",
  "details" : "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.\n\nThe 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.\n\nRegardless 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.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "silverstripe/framework"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "3.1.17"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 3.1.16"
    }
  }, {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "silverstripe/framework"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "3.2.0"
      }, {
        "fixed" : "3.2.2"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 3.2.1"
    }
  }, {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "silverstripe/framework"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "3.3.0-beta1"
      }, {
        "fixed" : "3.3.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/silverstripe/silverstripe-framework/commit/37059eb6b3546f304e9c031abca0f096ddb175c6"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/silverstripe/silverstripe-framework/commit/893e49703de4aa1855b5364919cbb0826f754fbf"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/silverstripe/silverstripe-framework/commit/faa94d51d570788dcebc2f2ef6e9de4d179ce1e4"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/FriendsOfPHP/security-advisories/blob/master/silverstripe/framework/SS-2016-003-1.yaml"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/silverstripe/silverstripe-framework"
  }, {
    "type" : "WEB",
    "url" : "https://www.silverstripe.org/download/security-releases/ss-2016-003"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2024-05-23T19:27:33Z",
    "nvd_published_at" : null
  }
}