Tomcat Windows Installer Creates Default Blank Administrative Password
SecurityTracker Alert ID: 1023146|
SecurityTracker URL: http://securitytracker.com/id/1023146
(Links to External Site)
Date: Nov 9 2009
User access via network|
Fix Available: Yes Vendor Confirmed: Yes Exploit Included: Yes |
Version(s): 5.5.0 to 5.5.28, 6.0.0 to 6.0.20; prior versions may also be affected.|
A vulnerability was reported in Tomcat. A remote user can gain administrative access to the target application.|
The Windows installer creates a blank password by default for the administrative user. If the password is not changed during installation, a remote user can gain access to the account.
David Horheim reported this vulnerability.
A remote user can gain administrative access to the target application in certain cases.|
The vendor has issued a source code fix.|
Vendor URL: tomcat.apache.org/ (Links to External Site)
|Underlying OS: Windows (Any)|
This archive entry has one or more follow-up message(s) listed below.|
Source Message Contents
Subject: [SECURITY] CVE-2009-3548 Apache Tomcat Windows Installer insecure default administrative password|
CVE-2009-3548: Apache Tomcat Windows Installer insecure default
The Apache Software Foundation
Tomcat 5.5.0 to 5.5.28
Tomcat 6.0.0 to 6.0.20
The unsupported Tomcat 3.x, 4.0.x, 4.1.x and 5.0.x versions may be also
The Windows installer defaults to a blank password for the
administrative user. If this is not changed during the install process,
then by default a user is created with the name admin, roles admin and
manager and a blank password.
Users of all Tomcat versions may mitigate this issue by one of the
- Using the .zip or .tar.gz distributions
- Specifying a strong password for the admin user when using the
- Removing the admin user from the tomcat-users.xml file after the
Windows installer has completed
- Editing the tomcat-users.xml file to provide the admin user with
a strong password after the Windows installer has completed
A patch for this issue  has been applied to trunk and will be
included in the next releases of 6.0.x and 5.5.x
This issue was reported directly  to the tomcat users public mailing
list by David Horheim.
Security researchers are reminded that undisclosed vulnerabilities in
Apache Tomcat should, in the first instance, be reported to the private
security mailing list.