# CVE-2016-5386: Server-side request forgery in n/a

> Remote attackers can redirect CGI application outbound traffic to arbitrary proxies via crafted Proxy headers, potentially exposing internal data or bypassing security controls.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 19 Jul 2016
- **Updated:** 6 Aug 2024
- **Also known as:** AZL-78994, AZL-98904, CVE-2016-1000101, GHSA-9hq4-732f-9vgf, GO-2022-0761, MGASA-2016-0317, UBUNTU-CVE-2016-5386, openSUSE-SU-2016:2054-1, openSUSE-SU-2016:2055-1, openSUSE-SU-2016:2536-1

## What is CVE-2016-5386?

CVE-2016-5386 is a high-severity server-side request forgery vulnerability in Fedoraproject Fedora, published on 19 Jul 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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 HTTP_PROXY 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.

Weakness: CWE-284 (Improper Access Control)

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

1 open source package ship an affected version, including stdlib. It affects 6 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `stdlib` | Go | All versions | 1.6.3 |
| `go` | SUSE:Package Hub 12 | All versions | 1.6.1-6.1 |
| `go` | SUSE:Package Hub 12 | All versions | 1.6.1-6.1 |
| `go1.4` | SUSE:Package Hub 12 | All versions | 1.4.3-6.1 |

Products: Fedoraproject Fedora, Golang Go, Oracle Linux, Redhat Enterprise Linux Server, Redhat Enterprise Linux Server Aus, Redhat Enterprise Linux Server Eus.

## How do I fix CVE-2016-5386?

Upgrade stdlib to 1.6.3 or later.

## Is CVE-2016-5386 being exploited?

There is no known exploitation of CVE-2016-5386 in the wild and no public exploit code.

## Other vulnerabilities in Fedoraproject Fedora

- [CVE-2024-4577](https://insights.sbomify.com/CVE-2024-4577/): PHP-CGI OS Command Injection (critical 9.8, exploited in the wild)
- [CVE-2021-39226](https://insights.sbomify.com/CVE-2021-39226/): Grafana Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2019-5544](https://insights.sbomify.com/CVE-2019-5544/): VMware ESXi and Horizon DaaS OpenSLP Heap-Based Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2024-4947](https://insights.sbomify.com/CVE-2024-4947/): Google Chromium V8 Type Confusion (critical 9.6, exploited in the wild)
- [CVE-2024-4671](https://insights.sbomify.com/CVE-2024-4671/): Google Chromium Visuals Use-After-Free (critical 9.6, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-5386 and fix it if it is affected.

What it is: CVE-2016-5386 is a high-severity server-side request forgery vulnerability in Fedoraproject Fedora, published on 19 Jul 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-5386 in the wild and no public exploit code.

Affected packages and fixed versions:
- stdlib (Go): affected all versions; fixed in 1.6.3

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2016-5386/ (Markdown: https://insights.sbomify.com/CVE-2016-5386/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2016-5386
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2016-5386
- OSV: https://osv.dev/vulnerability/CVE-2016-5386

---
From sbomify Insights: https://insights.sbomify.com/CVE-2016-5386/
Summaries are generated and may contain mistakes; the official description above is the record.