CVE-2016-5387

CVE-2016-5387

Published · Updated

Follow this CVE+ Monitor apache2+ Monitor apache2

E-mail alert when it lands in KEV, gets a public PoC or its score goes up.

15Vexday Risk Score

No sign of exploitation. No public exploitation artifact known so far.

ssvc Trackepss 56%
What the vendors declare (VEX)

Official vendor statements in CSAF/VEX format: whether their product is affected, already fixed, or ruled out — and why. These are the vendor's assertions, not Vexday's judgment.

Red HatVEX document ↗
Affected
2 products
Red Hat JBoss Enterprise Application Platform 6 · Red Hat JBoss Enterprise Web Server 1
none_available: Affected
Fixed
32 products (443 components)
Red Hat JBoss Enterprise Web Server 2 for RHEL 6 Server · Red Hat JBoss Web Server 3.0 for RHEL 6 · Red Hat JBoss Web Server 3.0 for RHEL 7 · Red Hat Enterprise Linux (v. 5 server) · Red Hat JBoss Enterprise Web Server 2 for RHEL 7 Server · and others 27
fix ↗
Not affected
1 product — because the vulnerable code is not present in the product
Red Hat JBoss Enterprise Application Platform 7
The Apache HTTP Server through 2.4.23 follows RFC 3875 section 4.1.18 and therefore does not protect applications from the presence of untrusted client data in the HTTP_PROXY environment variable, which might allow remote attackers to redirect an application's outbound HTTP traffic to an arbitrary proxy server via a crafted Proxy header in an HTTP request, aka an "httpoxy" issue. NOTE: the vendor states "This mitigation has been assigned the identifier CVE-2016-5387"; in other words, this is not a CVE ID for a vulnerability.
Affected products
n/a · n/a