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

> Remote attackers can redirect outbound HTTP traffic to arbitrary proxies via crafted headers, enabling SSRF attacks against CGI applications.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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:** 19 Feb 2020
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-qhf2-73w2-gwfh, UBUNTU-CVE-2016-1000109

## What is CVE-2016-1000109?

CVE-2016-1000109 is a medium-severity server-side request forgery vulnerability in n/a, published on 19 Feb 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

HHVM 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. This issue affects HHVM versions prior to 3.9.6, all versions between 3.10.0 and 3.12.4 (inclusive), and all versions between 3.13.0 and 3.14.2 (inclusive).

Weakness: CWE-665 (Improper Initialization)

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

It affects 1 product.


Products: Facebook Hhvm.

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

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

## Is CVE-2016-1000109 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-36937](https://insights.sbomify.com/CVE-2022-36937/): HHVM 4.172.0 and all prior versions use TLS 1.0 for secure connections when handling tls:// URLs in the stream extension. (critical 9.8)
- [CVE-2020-1900](https://insights.sbomify.com/CVE-2020-1900/): Use after free in HHVM (critical 9.8)
- [CVE-2020-1916](https://insights.sbomify.com/CVE-2020-1916/): Integer overflow in HHVM (critical 9.8)
- [CVE-2020-1917](https://insights.sbomify.com/CVE-2020-1917/): Memory corruption in HHVM (critical 9.8)
- [CVE-2021-24025](https://insights.sbomify.com/CVE-2021-24025/): Integer overflow in HHVM (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2016-1000109 is a medium-severity server-side request forgery vulnerability in n/a, published on 19 Feb 2020. 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-1000109 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-1000109/ (Markdown: https://insights.sbomify.com/CVE-2016-1000109/index.md)
```

## Sources

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

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