{"items":[{"id":"NVI-00006708","kind":"vulnerability","title":"Silverstripe Hostname, IP and Protocol Spoofing through HTTP Headers","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-87pf-7x99-5xc4"],"plain_summary":"OSV carries this publisher advisory for silverstripe/framework, silverstripe/framework, silverstripe/framework. This is an aggregated source copy; consult the original publisher and compare update dates.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"The original advisory lists fixed boundaries 3.1.17 for silverstripe/framework. Confirm the publisher’s latest guidance.","source_ids":["sr-bf9da5f6f5fc7255d0d7c42ecb1caaac"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 3.2.2 for silverstripe/framework. Confirm the publisher’s latest guidance.","source_ids":["sr-bf9da5f6f5fc7255d0d7c42ecb1caaac"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 3.3.0 for silverstripe/framework. Confirm the publisher’s latest guidance.","source_ids":["sr-bf9da5f6f5fc7255d0d7c42ecb1caaac"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-bf9da5f6f5fc7255d0d7c42ecb1caaac","url":"https://github.com/advisories/GHSA-87pf-7x99-5xc4","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-87pf-7x99-5xc4","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:59.958Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-bf9da5f6f5fc7255d0d7c42ecb1caaac"],"technology":"silverstripe/framework","known_exclusions":[],"conditions_summary":"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 followi","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 3.1.17"]},{"certainty":"source_listed","source_ids":["sr-bf9da5f6f5fc7255d0d7c42ecb1caaac"],"technology":"silverstripe/framework","known_exclusions":[],"conditions_summary":"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 followi","public_affected_ranges":["ECOSYSTEM: introduced 3.2.0; fixed 3.2.2"]},{"certainty":"source_listed","source_ids":["sr-bf9da5f6f5fc7255d0d7c42ecb1caaac"],"technology":"silverstripe/framework","known_exclusions":[],"conditions_summary":"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 followi","public_affected_ranges":["ECOSYSTEM: introduced 3.3.0-beta1; fixed 3.3.0"]}],"null_published_at":"2026-10-31T22:13:10.069Z","source_updated_at":"2024-11-28T05:40:22.033Z","source_disclosed_at":"2024-05-23T19:27:33.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-10-31T21:41:59.958Z"}],"next_cursor":null,"snapshot_revision":"39771"}