CVE-2016-1000108

What it is

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.

At a glance

Exploitability

Can be exploited over the network without logging in, but needs a user to act. Limited direct impact.

Exploit odds

1.1% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2019-12-10 15:15 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 00:38 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 1.1% in the next 30 days (EPSS).
• Severity: 6.1 MEDIUM (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2019-12-10 15:15 UTC

Last modified

2026-06-17 00:38 UTC

Exploit probability

1.1% · EPSS, next 30 days

Weakness

CWE-601

Record status

Modified

Affected

• Yaws < 2.0.4
• Debian Linux 8.0
• Debian Linux 9.0
• Debian Linux 10.0

Attack profile CVSS 3.1 · 6.1

Attack vector

Network

Complexity

Low

Privileges needed

None

User interaction

Required

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

None

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2016-1000108.md and follow it. Check whether this project is affected by CVE-2016-1000108. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge