Vulnerabilities · 2016 · Yaws
CVE-2016-1000108
Yaws vulnerability
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.
Affected products
Yaws, Debian Linux. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Yaws runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/klacke/yaws/commit/9d8fb070e782c95821c90d0ca7372fc6d7316c78#diff-54053c47eb173a · Patch
- www.openwall.com/lists/oss-security/2016/07/18/6 · Third Party Advisory
- raw.githubusercontent.com/distributedweaknessfiling/cvelist/master/2016/1000xxx/CVE-2016-1 · Third Party Advisory
- security-tracker.debian.org/tracker/CVE-2016-1000108 · Third Party Advisory
- nvd.nist.gov/vuln/detail/CVE-2016-1000108
- cve.org/CVERecord?id=CVE-2016-1000108
More vulnerabilities in Yaws products
CVE-2020-24916CVE-2020-24379CVE-2020-12872CVE-2017-10974CVE-2011-5025CVE-2011-4350CVE-2010-4181CVE-2009-4495All 11
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.