CVE-2016-5386: High severity red hat fedora vulnerability

Published Jul 8, 2016
·
Updated

Dominic Scheirlinck of VendHQ reports:

Many software projects and vendors have implemented support for the “Proxy” request header in their respective CGI implementations and languages by creating the “HTTPPROXY” environmental variable based on the header value. When this variable is used (in many cases automatically by various HTTP client libraries) any outgoing requests generated in turn from the attackers original request can be redirected to an attacker controlled proxy. This allows attackers to view potentially sensitive information, reply with malformed data, or to hold connections open causing a potential denial of service.

The Go programming language can automatically populate the HTTPPROXY environmental variable with a user supplied "Proxy" header.

Other sources

Google Go net/http package could allow a remote attacker to redirect HTTP traffic of CGI application, caused by the failure to protect applications from the presence of untrusted client data in the HTTPPROXY environment variable. By using a specially-crafted Proxy header in a HTTP request, an attacker could exploit this vulnerability to redirect outbound HTTP traffic to arbitrary proxy server.

This is also known as the "HTTPOXY" vulnerability.

IBM

The net/http package in Go through 1.6 does not attempt to address RFC 3875 section 4.1.18 namespace conflicts and therefore does not protect CGI applications from the presence of untrusted client data in the HTTPPROXY environment variable, which might allow remote attackers to redirect a CGI application's outbound HTTP traffic to an arbitrary proxy server via a crafted Proxy header in an HTTP request, aka an "httpoxy" issue.

MITRE

Affected Software

10 affected componentsFixes available
redhat/Go<1.6.3
1.6.3
redhat/Go<1.7
1.7
Fedoraproject Fedora=23
Fedoraproject Fedora=24
Oracle Linux=7
redhat Enterprise Linux Server=7.0
redhat Enterprise Linux Server Aus=7.2
redhat Enterprise Linux Server Eus=7.2
Golang Go>=1.0<1.6.3
Golang Go=1.7-rc1

Event History

Jul 19, 2016
CVE Published
via MITRE·01:00 AM
Data Sourced
via MITRE·01:00 AM
Description
Feb 4, 2025
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software
Sep 3, 2025
Data Sourced
via Microsoft·11:29 PM
DescriptionSeverityWeakness

Parent advisories

This vulnerability appears in the following advisories.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2016-5386?

CVE-2016-5386 has a medium severity rating due to its potential impact on affected systems.

2

How do I fix CVE-2016-5386?

To fix CVE-2016-5386, you should upgrade the Go programming language to versions 1.6.3 or 1.7 or higher.

3

Which software versions are affected by CVE-2016-5386?

CVE-2016-5386 affects Go programming language versions prior to 1.6.3 and 1.7.

4

Is CVE-2016-5386 a remote vulnerability?

Yes, CVE-2016-5386 can be exploited remotely through manipulated proxy headers.

5

Who reported CVE-2016-5386?

CVE-2016-5386 was reported by Dominic Scheirlinck of VendHQ.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203