Apache Tomcat 7.x through 7.0.70 and 8.x through 8.5.4, when the CGI Servlet is enabled, follows RFC 3875 section 4.1.18 and therefore does
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 7.0.72, 8.5.5
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
Apache Tomcat 7.x through 7.0.70 and 8.x through 8.5.4, when the CGI Servlet is enabled, 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 "A mitigation is planned for future releases of Tomcat, tracked as CVE-2016-5388"; in other words, this is not a CVE ID for a vulnerability.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
- EPSS reached 10%
FIRST estimates at least a 10% chance of exploitation in the next 30 days
Affected versions
- org.apache.tomcat:tomcat-catalinaMaven
From 7.0.0 · fixed in 7.0.72
- org.apache.tomcat:tomcat-catalinaMaven
From 8.0.0 · fixed in 8.5.5
References 25
access.redhat.com
h20566.www2.hpe.com
kb.cert.org
oracle.com
tomcat.apache.org
securityfocus.com
lists.opensuse.org
apache.org
httpoxy.org
securitytracker.com
lists.debian.org
lists.apache.org
- thread.html/053d9ce4d579b02203db18545fee5e33f35f2932885459b74d1e4272@<issues.activemq.apache.org>
- thread.html/6d3d34adcf3dfc48e36342aa1f18ce3c20bb8e4c458a97508d5bfed1@<issues.activemq.apache.org>
- thread.html/6b414817c2b0bf351138911c8c922ec5dd577ebc0b9a7f42d705752d@<issues.activemq.apache.org>
- thread.html/rc6b2147532416cc736e68a32678d3947b7053c3085cf43a9874fd102@<users.tomcat.apache.org>
- thread.html/r2853582063cfd9e7fbae1e029ae004e6a83482ae9b70a698996353dd@<users.tomcat.apache.org>
- thread.html/rf21b368769ae70de4dee840a3228721ae442f1d51ad8742003aefe39@<users.tomcat.apache.org>