Authentication Bypass Using an Alternate Path or Channel in Apache Tomcat
In Apache Tomcat 9.0.0.M1 to 9.0.0.M9, 8.5.0 to 8.5.4, 8.0.0.RC1 to 8.0.36, 7.0.0 to 7.0.70 and 6.0.0 to 6.0.45 a malicious web application was able to bypass a configured SecurityManager via a Tomcat utility method that was accessible to web applications.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2016-5018US | critical9.1OT elevated | — | ||
In Apache Tomcat 9.0.0.M1 to 9.0.0.M9, 8.5.0 to 8.5.4, 8.0.0.RC1 to 8.0.36, 7.0.0 to 7.0.70 and 6.0.0 to 6.0.45 a malicious web application was able to bypass a configured Security… | ||||
02
references
External citations — patches, advisories, analysis.
- http://packetstormsecurity.com/files/155873/Tomcat-9.0.0.M1-Sandbox-Escape.htmlWEB
- http://rhn.redhat.com/errata/RHSA-2017-0457.htmlWEB
- http://rhn.redhat.com/errata/RHSA-2017-1551.htmlWEB
- http://www.debian.org/security/2016/dsa-3720WEB
- https://access.redhat.com/errata/RHSA-2017:0455WEB
- https://access.redhat.com/errata/RHSA-2017:0456WEB
- https://access.redhat.com/errata/RHSA-2017:1548WEB
- https://access.redhat.com/errata/RHSA-2017:1549WEB
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan