Apache Tomcat information exposure vulnerability
Security constraints defined by annotations of Servlets in Apache Tomcat 9.0.0.M1 to 9.0.4, 8.5.0 to 8.5.27, 8.0.0.RC1 to 8.0.49 and 7.0.0 to 7.0.84 were only applied once a Servlet had been loaded. Because security constraints defined in this way apply to the URL pattern and any URLs below that point, it was possible - depending on the order Servlets were loaded - for some security constraints not to be applied. This could have exposed resources to users who were not authorised to access them.
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2018-1305US | medium6.5 | Exploit | ||
Security constraints defined by annotations of Servlets in Apache Tomcat 9.0.0.M1 to 9.0.4, 8.5.0 to 8.5.27, 8.0.0.RC1 to 8.0.49 and 7.0.0 to 7.0.84 were only applied once a Servle… | ||||
references
External citations — patches, advisories, analysis.
- http://www.oracle.com/technetwork/security-advisory/cpujul2018-4258247.htmlWEB
- http://www.oracle.com/technetwork/security-advisory/cpuoct2018-4428296.htmlWEB
- https://access.redhat.com/errata/RHSA-2018:0465WEB
- https://access.redhat.com/errata/RHSA-2018:0466WEB
- https://access.redhat.com/errata/RHSA-2018:1320WEB
- https://access.redhat.com/errata/RHSA-2018:2939WEB
- https://access.redhat.com/errata/RHSA-2019:2205WEB
- https://github.com/apache/tomcatPACKAGE
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