CVE-2011-2204: Infoleak

Published Jun 27, 2011
·
Updated

Apache Tomcat 5.5.x before 5.5.34, 6.x before 6.0.33, and 7.x before 7.0.17, when the MemoryUserDatabase is used, creates log entries containing passwords upon encountering errors in JMX user creation, which allows local users to obtain sensitive information by reading a log file.

Other sources

Apache Tomcat 5.5.x before 5.5.34, 6.x before 6.0.33, and 7.x before 7.0.19, when the MemoryUserDatabase is used, creates log entries containing passwords upon encountering errors in JMX user creation, which allows local users to obtain sensitive information by reading a log file.

This issue was fixed in Apache Tomcat 7.0.17 but the release votes for the 7.0.17 and 7.0.18 release candidates did not pass. Therefore, users must download 7.0.19 to obtain a version that includes a fix.

GitHub

From the upstream advisory notes [1]:

When using the MemoryUserDatabase (based on tomcat-users.xml) and creating users via JMX, an exception during the user creation process may trigger an error message in the JMX client that includes the user's password. This error message is also written to the Tomcat logs. User passwords are visible to administrators with JMX access and/or administrators with read access to the tomcat-users.xml file. Users that do not have these permissions but are able to read log files may be able to discover a user's password.

This is fixed in Tomcat 5.5.34 (not yet released) [2] and Tomcat 6.0.33 (not yet released) [3].

[1] http://tomcat.apache.org/security-5.html [2] http://svn.apache.org/viewvc?view=revision&revision=1140072 [2] http://svn.apache.org/viewvc?view=revision&revision=1140071

Red Hat

Affected Software

84 affected componentsFixes available
maven/org.apache.tomcat:tomcat>=7.0.0<7.0.19
7.0.19
maven/org.apache.tomcat:tomcat>=6.0.0<6.0.33
6.0.33
maven/org.apache.tomcat:tomcat>=5.5.0<5.5.34
5.5.34
redhat/tomcat<5.5.34
5.5.34
redhat/tomcat<6.0.33
6.0.33
Apache Tomcat=5.5.0
Apache Tomcat=5.5.1
Apache Tomcat=5.5.2
Apache Tomcat=5.5.3
Apache Tomcat=5.5.4
Apache Tomcat=5.5.5
Apache Tomcat=5.5.6
Apache Tomcat=5.5.7
Apache Tomcat=5.5.8
Apache Tomcat=5.5.9
Apache Tomcat=5.5.10
Apache Tomcat=5.5.11
Apache Tomcat=5.5.12
Apache Tomcat=5.5.13
Apache Tomcat=5.5.14
Apache Tomcat=5.5.15
Apache Tomcat=5.5.16
Apache Tomcat=5.5.17
Apache Tomcat=5.5.18
Apache Tomcat=5.5.19
Apache Tomcat=5.5.20
Apache Tomcat=5.5.21
Apache Tomcat=5.5.22
Apache Tomcat=5.5.23
Apache Tomcat=5.5.24
Apache Tomcat=5.5.25
Apache Tomcat=5.5.26
Apache Tomcat=5.5.27
Apache Tomcat=5.5.28
Apache Tomcat=5.5.29
Apache Tomcat=5.5.30
Apache Tomcat=5.5.31
Apache Tomcat=5.5.32
Apache Tomcat=5.5.33
Apache Tomcat=6.0
Apache Tomcat=6.0.0
Apache Tomcat=6.0.1
Apache Tomcat=6.0.2
Apache Tomcat=6.0.3
Apache Tomcat=6.0.4
Apache Tomcat=6.0.5
Apache Tomcat=6.0.6
Apache Tomcat=6.0.7
Apache Tomcat=6.0.8
Apache Tomcat=6.0.9
Apache Tomcat=6.0.10
Apache Tomcat=6.0.11
Apache Tomcat=6.0.12
Apache Tomcat=6.0.13
Apache Tomcat=6.0.14
Apache Tomcat=6.0.15
Apache Tomcat=6.0.16
Apache Tomcat=6.0.17
Apache Tomcat=6.0.18
Apache Tomcat=6.0.19
Apache Tomcat=6.0.20
Apache Tomcat=6.0.24
Apache Tomcat=6.0.26
Apache Tomcat=6.0.27
Apache Tomcat=6.0.28
Apache Tomcat=6.0.29
Apache Tomcat=6.0.30
Apache Tomcat=6.0.31
Apache Tomcat=6.0.32
Apache Tomcat=7.0.0
Apache Tomcat=7.0.0-beta
Apache Tomcat=7.0.1
Apache Tomcat=7.0.2
Apache Tomcat=7.0.3
Apache Tomcat=7.0.4
Apache Tomcat=7.0.5
Apache Tomcat=7.0.6
Apache Tomcat=7.0.7
Apache Tomcat=7.0.8
Apache Tomcat=7.0.9
Apache Tomcat=7.0.10
Apache Tomcat=7.0.11
Apache Tomcat=7.0.12
Apache Tomcat=7.0.14

Event History

Jun 29, 2011
CVE Published
via MITRE·05:00 PM
Data Sourced
via MITRE·05:00 PM
Description
May 14, 2022
Advisory Published
via GitHub·01:17 AM

Frequently Asked Questions

1

What is the severity of CVE-2011-2204?

CVE-2011-2204 has been classified as a medium severity vulnerability, primarily due to the potential exposure of sensitive information.

2

How do I fix CVE-2011-2204?

To fix CVE-2011-2204, upgrade to Apache Tomcat version 5.5.34, 6.0.33, or 7.0.17 or later.

3

What versions of Apache Tomcat are affected by CVE-2011-2204?

CVE-2011-2204 affects Apache Tomcat versions prior to 5.5.34, 6.0.33, and 7.0.17.

4

What type of information is exposed in CVE-2011-2204?

CVE-2011-2204 could expose usernames and passwords in the log files when errors occur during JMX user creation.

5

Who can exploit CVE-2011-2204?

CVE-2011-2204 can be exploited by local users who have access to the log files where sensitive information is written.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203