CVE-2016-1000109
Last modified
CVE-2016-1000109 is a medium-severity vulnerability rated 5.3/10 on the CVSS scale. 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).. EPSS estimates a 4.95% chance of exploitation in the next 30 days.
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).
Metrics
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Hhvm | < 3.9.6 | |
| Hhvm | >= 3.10.0, <= 3.12.4 | |
| Hhvm | >= 3.13.0, <= 3.14.2 |
References
- https://github.com/facebook/hhvm/commit/423b4b719afd5ef4e6e19d8447fbf7b6bc0d0a25Patch, Third Party Advisory
- https://httpoxy.org/Exploit, Mitigation, Third Party Advisory
- https://www.facebook.com/security/advisories/cve-2016-1000109Third Party Advisory
- https://github.com/facebook/hhvm/commit/423b4b719afd5ef4e6e19d8447fbf7b6bc0d0a25Patch, Third Party Advisory
- https://httpoxy.org/Exploit, Mitigation, Third Party Advisory
- https://www.facebook.com/security/advisories/cve-2016-1000109Third Party Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2016-1000109?
How severe is CVE-2016-1000109?
How do I fix CVE-2016-1000109?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2016
- CVE-2016-1000103Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultID…
- CVE-2016-1000104A security Bypass vulnerability exists in the FcgidPassHeade…8.8
- CVE-2016-1000105Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultID…
- CVE-2016-1000106Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultID…
- CVE-2016-1000107inets in Erlang possibly 22.1 and earlier follows RFC 3875 s…6.1
- CVE-2016-1000108yaws before 2.0.4 does not attempt to address RFC 3875 secti…6.1
- CVE-2016-1000110The CGIHandler class in Python before 2.7.12 does not protec…6.1
- CVE-2016-1000111Twisted before 16.3.1 does not attempt to address RFC 3875 s…5.3
- CVE-2016-1000112Unauthenticated remote .jpg file upload in contus-video-comm…9.1
- CVE-2016-1000113XSS and SQLi in huge IT gallery v1.1.5 for Joomla9.8
- CVE-2016-1000114XSS in huge IT gallery v1.1.5 for Joomla6.1
- CVE-2016-1000115Huge-IT Portfolio Gallery manager v1.1.0 SQL Injection and X…
Are you affected by CVE-2016-1000109?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST