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

> Attackers can redirect CGI traffic to malicious proxies via the httpoxy vulnerability in spiffy-cgi-handlers, potentially intercepting or modifying data.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Jan 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-h8x6-23c3-3g6v

## What is CVE-2016-6286?

CVE-2016-6286 is a high-severity server-side request forgery vulnerability in n/a, published on 10 Jan 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The "spiffy-cgi-handlers" egg would convert a nonexistent "Proxy" header to the HTTP_PROXY environment variable, which would allow attackers to direct CGI programs which use this environment variable to use an attacker-specified HTTP proxy server (also known as a "httpoxy" attack). This affects all versions of spiffy-cgi-handlers before 0.5.

Weakness: CWE-19

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

It affects 1 product.


Products: Call-Cc Http-Client.

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

No fix has been published for CVE-2016-6286 yet. Limit exposure of the affected software until one is available.

## Is CVE-2016-6286 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2016-6287](https://insights.sbomify.com/CVE-2016-6287/): Server-side request forgery in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2016-6286 is a high-severity server-side request forgery vulnerability in n/a, published on 10 Jan 2017. 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-6286 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-6286/ (Markdown: https://insights.sbomify.com/CVE-2016-6286/index.md)
```

## Sources

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

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