First published: Tue Dec 10 2019(Updated: )
yaws before 2.0.4 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.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
debian/yaws | 2.0.8+dfsg-3 2.1.1+dfsg-2 2.2.0+dfsg-1 | |
Yaws | <2.0.4 | |
Debian Linux | =8.0 | |
Debian Linux | =9.0 | |
Debian Linux | =10.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2016-1000108 is considered a moderate severity vulnerability due to the potential for remote attackers to manipulate CGI applications.
To fix CVE-2016-1000108, upgrade yaws to version 2.0.8+dfsg-3 or later.
CVE-2016-1000108 affects yaws versions prior to 2.0.4 on Debian GNU/Linux systems.
CVE-2016-1000108 allows attackers to redirect a CGI application's outbound HTTP requests by exploiting untrusted client data.
Yes, CVE-2016-1000108 does not comply with RFC 3875 section 4.1.18 regarding namespace conflicts.