System Property Disclosure in Apache Tomcat
Apache Software Foundation Apache Tomcat
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| org.apache.tomcat:tomcat Maven |
|
|
Apache Software Foundation Apache Tomcat
| Product | Affected | Fixed in |
|---|---|---|
| org.apache.tomcat:tomcat Maven |
|
|
8.5.59.0.0.M10When a SecurityManager is configured, a web application's ability to read system properties should be controlled by the SecurityManager. 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, 6.0.0 to 6.0.45 the system property replacement feature for configuration files could be used by a malicious web application to bypass the SecurityManager and read system properties that should not be visible.
From the CVE record · apache
When a SecurityManager is configured, a malicious web application can use system property replacement in configuration files to read system properties it should not be allowed to see. This requires the malicious web application to run in the affected Tomcat instance; the input does not specify an authentication or user-interaction requirement.
Operators of Apache Tomcat or the Maven package org.apache.tomcat:tomcat should check versions 6.0.0–6.0.46, 7.0.0–7.0.71, 8.0.0–8.0.36, 8.1.0–8.5.4, and 9.0.0.M1–9.0.0.M9.