Skip to content

HTTP Proxy header vulnerability

High severity GitHub Reviewed Published Apr 7, 2022 to the GitHub Advisory Database • Updated Feb 5, 2024

Package

composer amphp/artax (Composer)

Affected versions

>= 2.0.0, < 2.0.4
> 0.7.1, < 1.0.4

Patched versions

2.0.4
1.0.4
composer bugsnag/bugsnag-laravel (Composer)
>= 2, < 2.0.2
2.0.2
composer drupal/core (Composer)
>= 8.0, < 8.1.7
8.1.7
composer drupal/drupal (Composer)
>= 8.0, < 8.1.7
8.1.7
composer guzzlehttp/guzzle (Composer)
>= 6, < 6.2.1
>= 4.0.0-rc2, < 4.2.4
>= 5, < 5.3.1
6.2.1
4.2.4
5.3.1
composer padraic/humbug_get_contents (Composer)
< 1.1.2
1.1.2
composer typo3/cms (Composer)
>= 8.0.0, < 8.2.1
8.2.1

Description

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.

References

Published by the National Vulnerability Database Jul 19, 2016
Published to the GitHub Advisory Database Apr 7, 2022
Reviewed Apr 7, 2022
Last updated Feb 5, 2024

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS score

92.761%
(99th percentile)

Weaknesses

CVE ID

CVE-2016-5385

GHSA ID

GHSA-m6ch-gg5f-wxx3

Source code

No known source code
Loading Checking history
Improvements are not currently accepted on this advisory because it uses an unsupported versioning operator. Read more and discuss here.