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.
References
Link | Resource |
---|---|
http://www.openwall.com/lists/oss-security/2016/07/18/6 | Mailing List Third Party Advisory |
https://raw.githubusercontent.com/distributedweaknessfiling/cvelist/master/2016/1000xxx/CVE-2016-1000108.json | Third Party Advisory |
https://security-tracker.debian.org/tracker/CVE-2016-1000108 | Third Party Advisory |
https://github.com/klacke/yaws/commit/9d8fb070e782c95821c90d0ca7372fc6d7316c78#diff-54053c47eb173a90c26ed19bd9d106c1 | Patch Third Party Advisory |
Information
Published : 2019-12-10 07:15
Updated : 2020-08-18 08:05
NVD link : CVE-2016-1000108
Mitre link : CVE-2016-1000108
JSON object : View
CWE
CWE-601
URL Redirection to Untrusted Site ('Open Redirect')
Products Affected
debian
- debian_linux
yaws
- yaws