CVE-2016-1000108: n/a vulnerability

CVE-2016-1000108: yaws before 2.0.4 does not attempt to address RFC 3875 section 4.1.18 namespace conflicts and therefore doe...

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.

UnknownCVSS not scoredNot KEV-listedUpdatedAug 6, 2024, 03:55 UTC (UTC+00:00)

Security readout for executives and security teams

Affected Yaws versions can pass attacker-controlled Proxy request header data into CGI environment variables. A vulnerable CGI application may then send its own outbound HTTP traffic through an attacker-chosen proxy, creating risk of interception, redirection, or manipulation of server-side requests. Exposure is likely limited to deployments running Yaws before 2.0.4 with CGI applications that make outbound HTTP requests and honor HTTP_PROXY-style environment proxy settings. Treat this as a targeted legacy web-server risk. It is not flagged as actively exploited in the provided sources, but affected internet-facing CGI services can expose sensitive outbound traffic paths and should be upgraded or hardened. Mitigation focus: Upgrade Yaws deployments earlier than 2.0.4 to 2.0.4 or later.; Review vendor and distribution guidance for httpoxy-specific hardening.; Block or unset untrusted Proxy request headers before they reach CGI execution..

Prepared: Jun 6, 2026, 03:53 UTC (UTC+00:00)

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2016-1000108 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup

Vulnerability profileCVE Program record

Severity: Unknown
CVSS: Not scored
Known Exploited: No
Published: Dec 10, 2019, 14:58 UTC (UTC+00:00)

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors

0Timeline events

0ADP providers

4Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

CVE List V5 sourceCVE List V5
https://raw.githubusercontent.com/distributedweaknessfiling/cvelist/master/2016/1000xxx/CVE-2016-1000108.jsonCVE reference · x_refsource_MISC
https://security-tracker.debian.org/tracker/CVE-2016-1000108CVE reference · x_refsource_MISC
https://github.com/klacke/yaws/commit/9d8fb070e782c95821c90d0ca7372fc6d7316c78#diff-54053c47eb173a90c26ed19bd9d106c1CVE reference · x_refsource_CONFIRM

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus

n/an/an/aListed

Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.