HTTP Proxy header vulnerability
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| guzzlehttp/guzzle Packagist |
|
|
| drupal/core Packagist |
| Product | Affected | Fixed in |
|---|---|---|
| guzzlehttp/guzzle Packagist |
|
|
| drupal/core Packagist |
≥ 8.0 · < 8.1.7
|
| bugsnag/bugsnag-laravel Packagist |
|
|
| amphp/artax Packagist |
|
|
| padraic/humbug_get_contents Packagist |
|
|
PHP through 7.0.8 does not attempt to address RFC 3875 section 4.1.18 namespace conflicts and therefore does not protect applications from the presence of untrusted client data in the HTTP_PROXY environment variable, which might allow remote attackers to redirect an application's outbound HTTP traffic to an arbitrary proxy server via a crafted Proxy header in an HTTP request, as demonstrated by (1) an application that makes a getenv('HTTP_PROXY') call or (2) a CGI configuration of PHP, aka an "httpoxy" issue.
From the CVE record · redhat
PHP through 7.0.8 does not protect applications from untrusted client data in the HTTP_PROXY environment variable. A remote attacker may redirect an application's outbound HTTP traffic to an arbitrary proxy by sending a crafted Proxy header when the application calls getenv('HTTP_PROXY') or runs in a CGI configuration of PHP.
Engineers running PHP through 7.0.8, or the listed affected versions of guzzlehttp/guzzle, drupal/core, bugsnag/bugsnag-laravel, amphp/artax, or padraic/humbug_get_contents, should check their deployments.