HTTP Proxy header vulnerability
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.
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2016-5385US | high8.1 | — | ||
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… | ||||
references
External citations — patches, advisories, analysis.
- http://lists.opensuse.org/opensuse-updates/2016-08/msg00003.htmlWEB
- http://rhn.redhat.com/errata/RHSA-2016-1609.htmlWEB
- http://rhn.redhat.com/errata/RHSA-2016-1610.htmlWEB
- http://rhn.redhat.com/errata/RHSA-2016-1611.htmlWEB
- http://rhn.redhat.com/errata/RHSA-2016-1612.htmlWEB
- http://rhn.redhat.com/errata/RHSA-2016-1613.htmlWEB
- http://www.debian.org/security/2016/dsa-3631WEB
- http://www.kb.cert.org/vuls/id/797896WEB
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan