Notified: July 12, 2016 Updated: July 12, 2016
Unknown
No statement is currently available from the vendor regarding this vulnerability.
Notified: July 12, 2016 Updated: July 12, 2016
Unknown
No statement is currently available from the vendor regarding this vulnerability.
Notified: July 12, 2016 Updated: July 18, 2016
Statement Date: July 14, 2016
Affected
The Apache Software Foundation has discovered no examples of condition 2 described in the [redacted] report, and has determined there is no "vulnerability" per se in ASF software, which conform to both RFC822 (circa 1982) and CGI/1.1 defacto standard (circa 1995, superseded by CGI/1.1 IANA spec RFC 3875). Several ASF projects participate in HTTP requests in the manners described under condition 1. The list of projects that will offer one or more mitigations include but are not limited to; Apache HTTP Server (httpd) (Tracked as CVE-2016-5387) Apache Tomcat Server (Tracked as CVE-2016-5388) Apache Traffic Server (ATS) (Tracking is not applicable) Projects and subprojects impacted by the Apache HTTP Server mitigations will include mod_fcgid (Apache HTTP Project) and mod_perl (Apache Perl Project), as well as external projects such as mod_wsgi, all hopefully under CVE-2016-5387. Note specifically that any CVE related to mod_fcgi[d] must be ignored, as it duplicates CVE-2016-5387. We have not reached a conclusion on separate tracking that might be unique to mod_perl itself (thus far, it also appears to duplicate -5387.)
We are not aware of further vendor information regarding this vulnerability.
Notified: July 12, 2016 Updated: July 12, 2016
Unknown
No statement is currently available from the vendor regarding this vulnerability.
We are not aware of further vendor information regarding this vulnerability.
Notified: July 12, 2016 Updated: July 12, 2016
Unknown
No statement is currently available from the vendor regarding this vulnerability.
Notified: July 12, 2016 Updated: July 12, 2016
Unknown
No statement is currently available from the vendor regarding this vulnerability.
Notified: July 12, 2016 Updated: July 12, 2016
Unknown
No statement is currently available from the vendor regarding this vulnerability.
Notified: July 12, 2016 Updated: July 12, 2016
Unknown
No statement is currently available from the vendor regarding this vulnerability.
Notified: July 12, 2016 Updated: July 12, 2016
Unknown
No statement is currently available from the vendor regarding this vulnerability.
Notified: July 12, 2016 Updated: July 12, 2016
Unknown
No statement is currently available from the vendor regarding this vulnerability.
Notified: July 12, 2016 Updated: July 12, 2016
Unknown
No statement is currently available from the vendor regarding this vulnerability.
Notified: July 12, 2016 Updated: July 12, 2016
Unknown
No statement is currently available from the vendor regarding this vulnerability.
Notified: July 12, 2016 Updated: July 12, 2016
Unknown
No statement is currently available from the vendor regarding this vulnerability.
Notified: July 12, 2016 Updated: July 12, 2016
Unknown
No statement is currently available from the vendor regarding this vulnerability.
Notified: July 12, 2016 Updated: July 12, 2016
Unknown
No statement is currently available from the vendor regarding this vulnerability.
Notified: July 12, 2016 Updated: July 12, 2016
Unknown
No statement is currently available from the vendor regarding this vulnerability.
Notified: July 12, 2016 Updated: July 12, 2016
Unknown
No statement is currently available from the vendor regarding this vulnerability.
Notified: July 12, 2016 Updated: July 12, 2016
Unknown
No statement is currently available from the vendor regarding this vulnerability.
Notified: July 12, 2016 Updated: July 12, 2016
Unknown
No statement is currently available from the vendor regarding this vulnerability.
Notified: July 12, 2016 Updated: July 12, 2016
Unknown
No statement is currently available from the vendor regarding this vulnerability.
Notified: July 12, 2016 Updated: July 12, 2016
Unknown
No statement is currently available from the vendor regarding this vulnerability.
Notified: July 12, 2016 Updated: July 12, 2016
Statement Date: July 12, 2016
Not Affected
Please find the EfficientIP’s status about VU#797896: Vendor: EfficientIP Status: Not Affected Statement: No version of our software is affected by VU#797896
We are not aware of further vendor information regarding this vulnerability.
Notified: July 12, 2016 Updated: July 12, 2016
Unknown
No statement is currently available from the vendor regarding this vulnerability.
Notified: July 12, 2016 Updated: July 12, 2016
Unknown
No statement is currently available from the vendor regarding this vulnerability.
Notified: July 12, 2016 Updated: July 12, 2016
Unknown
No statement is currently available from the vendor regarding this vulnerability.
Notified: July 12, 2016 Updated: July 12, 2016
Unknown
No statement is currently available from the vendor regarding this vulnerability.
Notified: July 12, 2016 Updated: July 12, 2016
Unknown
No statement is currently available from the vendor regarding this vulnerability.
Notified: July 12, 2016 Updated: July 12, 2016
Unknown
No statement is currently available from the vendor regarding this vulnerability.
Notified: July 12, 2016 Updated: July 12, 2016
Unknown
No statement is currently available from the vendor regarding this vulnerability.
Notified: July 12, 2016 Updated: July 12, 2016
Unknown
No statement is currently available from the vendor regarding this vulnerability.
Notified: July 12, 2016 Updated: July 12, 2016
Unknown
No statement is currently available from the vendor regarding this vulnerability.
Notified: July 12, 2016 Updated: July 12, 2016
Unknown
No statement is currently available from the vendor regarding this vulnerability.
Updated: July 18, 2016
Affected
No statement is currently available from the vendor regarding this vulnerability.
CVE-2016-5386
Updated: July 13, 2016
Affected
No statement is currently available from the vendor regarding this vulnerability.
We are not aware of further vendor information regarding this vulnerability.
Notified: July 12, 2016 Updated: July 12, 2016
Unknown
No statement is currently available from the vendor regarding this vulnerability.
Notified: July 12, 2016 Updated: July 12, 2016
Unknown
No statement is currently available from the vendor regarding this vulnerability.
Updated: July 18, 2016
Affected
No statement is currently available from the vendor regarding this vulnerability.
CVE-2016-1000109
Notified: July 12, 2016 Updated: July 12, 2016
Unknown
No statement is currently available from the vendor regarding this vulnerability.
Notified: July 12, 2016 Updated: July 12, 2016
Unknown
No statement is currently available from the vendor regarding this vulnerability.
Notified: July 12, 2016 Updated: July 12, 2016
Unknown
No statement is currently available from the vendor regarding this vulnerability.
Notified: July 12, 2016 Updated: July 12, 2016
Unknown
No statement is currently available from the vendor regarding this vulnerability.
Notified: July 12, 2016 Updated: July 12, 2016
Unknown
No statement is currently available from the vendor regarding this vulnerability.
Notified: July 12, 2016 Updated: July 12, 2016
Unknown
No statement is currently available from the vendor regarding this vulnerability.
Notified: July 12, 2016 Updated: July 12, 2016
Unknown
No statement is currently available from the vendor regarding this vulnerability.
Notified: July 12, 2016 Updated: July 12, 2016
Unknown
No statement is currently available from the vendor regarding this vulnerability.
Notified: July 12, 2016 Updated: July 12, 2016
Unknown
No statement is currently available from the vendor regarding this vulnerability.
Updated: July 19, 2016
Statement Date: July 19, 2016
Affected
Mitigation of httpoxy is available in lighttpd. Mitigation: lighttpd <= 1.4.40 (reject requests containing "Proxy" header) * Create "/path/to/deny-proxy.lua", read-only to lighttpd, with content: if (lighty.request["Proxy"] == nil) then return 0 else return 403 end * Modify lighttpd.conf to load mod_magnet and run lua code server.modules += ( "mod_magnet" ) magnet.attract-raw-url-to = ( "/path/to/deny-proxy.lua" ) lighttpd2 (development) (strip "Proxy" header from request) * Add to lighttpd.conf: req_header.remove "Proxy"; Reference: * lighttpd 1.4 repo contains fix on git master branch to strip "Proxy" header and the commit message below contains the above mitigation steps for lighttpd 1.4.x https://redmine.lighttpd.net/projects/lighttpd/repository/revisions/779c133c16f9af168b004dce7a2a64f16c1cb3a4
We are not aware of further vendor information regarding this vulnerability.
Notified: July 12, 2016 Updated: July 12, 2016
Unknown
No statement is currently available from the vendor regarding this vulnerability.
Notified: July 12, 2016 Updated: July 12, 2016
Unknown
No statement is currently available from the vendor regarding this vulnerability.
Notified: July 12, 2016 Updated: July 13, 2016
Affected
If you have installed PHP or any other third party framework on top of IIS, we recommend applying mitigation steps to protect from malicious Redirection or MiM attacks. Mitigation: Update apphost.config with the following rule:
We are not aware of further vendor information regarding this vulnerability.
Notified: July 12, 2016 Updated: July 12, 2016
Unknown
No statement is currently available from the vendor regarding this vulnerability.
Notified: July 12, 2016 Updated: July 12, 2016
Unknown
No statement is currently available from the vendor regarding this vulnerability.
Notified: July 12, 2016 Updated: July 12, 2016
Unknown
No statement is currently available from the vendor regarding this vulnerability.
Updated: July 13, 2016
Affected
No statement is currently available from the vendor regarding this vulnerability.
We are not aware of further vendor information regarding this vulnerability.
Notified: July 12, 2016 Updated: July 12, 2016
Unknown
No statement is currently available from the vendor regarding this vulnerability.
Notified: July 12, 2016 Updated: July 12, 2016
Unknown
No statement is currently available from the vendor regarding this vulnerability.
Notified: July 12, 2016 Updated: July 12, 2016
Unknown
No statement is currently available from the vendor regarding this vulnerability.
Notified: July 12, 2016 Updated: July 12, 2016
Unknown
No statement is currently available from the vendor regarding this vulnerability.
Notified: July 12, 2016 Updated: July 12, 2016
Unknown
No statement is currently available from the vendor regarding this vulnerability.
Notified: July 12, 2016 Updated: July 12, 2016
Unknown
No statement is currently available from the vendor regarding this vulnerability.
Notified: July 12, 2016 Updated: July 12, 2016
Unknown
No statement is currently available from the vendor regarding this vulnerability.
Notified: July 12, 2016 Updated: July 12, 2016
Unknown
No statement is currently available from the vendor regarding this vulnerability.
Notified: July 12, 2016 Updated: July 12, 2016
Unknown
No statement is currently available from the vendor regarding this vulnerability.
Notified: July 12, 2016 Updated: July 12, 2016
Unknown
No statement is currently available from the vendor regarding this vulnerability.
Updated: July 18, 2016
Affected
No statement is currently available from the vendor regarding this vulnerability.
CVE-2016-1000110
Notified: July 12, 2016 Updated: July 12, 2016
Unknown
No statement is currently available from the vendor regarding this vulnerability.
Notified: July 12, 2016 Updated: July 12, 2016
Unknown
No statement is currently available from the vendor regarding this vulnerability.
Notified: July 12, 2016 Updated: July 12, 2016
Unknown
No statement is currently available from the vendor regarding this vulnerability.
Notified: July 12, 2016 Updated: July 12, 2016
Unknown
No statement is currently available from the vendor regarding this vulnerability.
Notified: July 12, 2016 Updated: July 12, 2016
Unknown
No statement is currently available from the vendor regarding this vulnerability.
Updated: July 18, 2016
Unknown
No statement is currently available from the vendor regarding this vulnerability.
We are not aware of further vendor information regarding this vulnerability.
Notified: July 12, 2016 Updated: July 12, 2016
Unknown
No statement is currently available from the vendor regarding this vulnerability.
Notified: July 12, 2016 Updated: July 12, 2016
Unknown
No statement is currently available from the vendor regarding this vulnerability.
Notified: July 12, 2016 Updated: July 12, 2016
Unknown
No statement is currently available from the vendor regarding this vulnerability.
Notified: July 12, 2016 Updated: July 12, 2016
Unknown
No statement is currently available from the vendor regarding this vulnerability.
Notified: July 12, 2016 Updated: July 12, 2016
Unknown
No statement is currently available from the vendor regarding this vulnerability.
Notified: July 12, 2016 Updated: July 12, 2016
Unknown
No statement is currently available from the vendor regarding this vulnerability.
Notified: July 12, 2016 Updated: July 12, 2016
Unknown
No statement is currently available from the vendor regarding this vulnerability.
Notified: July 12, 2016 Updated: July 12, 2016
Unknown
No statement is currently available from the vendor regarding this vulnerability.
Notified: July 12, 2016 Updated: July 12, 2016
Unknown
No statement is currently available from the vendor regarding this vulnerability.
Updated: July 18, 2016
Affected
No statement is currently available from the vendor regarding this vulnerability.
CVE-2016-5385
Notified: July 12, 2016 Updated: July 12, 2016
Unknown
No statement is currently available from the vendor regarding this vulnerability.
Notified: July 12, 2016 Updated: July 12, 2016
Unknown
No statement is currently available from the vendor regarding this vulnerability.
Notified: July 12, 2016 Updated: July 12, 2016
Unknown
No statement is currently available from the vendor regarding this vulnerability.
Notified: July 12, 2016 Updated: July 12, 2016
Unknown
No statement is currently available from the vendor regarding this vulnerability.
Notified: July 12, 2016 Updated: July 12, 2016
Unknown
No statement is currently available from the vendor regarding this vulnerability.
Notified: July 12, 2016 Updated: July 12, 2016
Unknown
No statement is currently available from the vendor regarding this vulnerability.