SecurityTracker.com
Keep Track of the Latest Vulnerabilities
with SecurityTracker!
    Home    |    View Topics    |    Search    |    Contact Us    |   

SecurityTracker
Archives


 
Sign Up
Sign Up for Your FREE Weekly SecurityTracker E-mail Alert Summary
Instant Alerts
Buy our Premium Vulnerability Notification Service to receive customized, instant alerts
Affiliates
Put SecurityTracker Vulnerability Alerts on Your Web Site -- It's Free!
Partners
Become a Partner and License Our Database or Notification Service
Report a Bug
Report a vulnerability that you have found to SecurityTracker
bugs
@
securitytracker.com






Category:   Application (Web Server/CGI)  >   Apache Tomcat Vendors:   Apache Software Foundation
Tomcat Authentication Response Error Lets Remote Users Determine Valid Usernames
SecurityTracker Alert ID:  1022332
SecurityTracker URL:  http://securitytracker.com/id/1022332
CVE Reference:   CVE-2009-0580   (Links to External Site)
Date:  Jun 4 2009
Impact:   Disclosure of system information
Fix Available:  Yes  Vendor Confirmed:  Yes  Exploit Included:  Yes  
Version(s): 4.1.0 to 4.1.39, 5.5.0 to 5.5.27, 6.0.0 to 6.0.18
Description:   A vulnerability was reported in Apache Tomcat. A remote user can determine valid usernames on the target system.

In certain configurations, a remote user can send specially encoded password values to determine if the specified username exists on the target system.

Systems using form-based authentication (j_security_check) with one of the following
authentication realms are affected:

MemoryRealm
DataSourceRealm
JDBCRealm

D. Matscheko and T. Hackner of SEC Consult reported this vulnerability.

Impact:   A remote user can determine valid usernames on the target system.
Solution:   The vendor has issued a fix (6.0.20). The fix will be included in future versions 4.1.40 and 5.5.28.
Vendor URL:  tomcat.apache.org/ (Links to External Site)
Cause:   Access control error
Underlying OS:   Linux (Any), UNIX (Any), Windows (Any)

Message History:   This archive entry has one or more follow-up message(s) listed below.
Jul 6 2009 (Red Hat Issues Fix for JBoss) Tomcat Authentication Response Error Lets Remote Users Determine Valid Usernames   (bugzilla@redhat.com)
Red Hat has released a fix for JBoss Enterprise Application Platform (JBEAP) 4.2 for Red Hat Enterprise Linux 5.
Sep 21 2009 (Red Hat Issues Fix for JBoss) Tomcat Authentication Response Error Lets Remote Users Determine Valid Usernames   (bugzilla@redhat.com)
Red Hat has released a fix for JBoss Enterprise Web Server 1.0.0 for Red Hat Enterprise Linux 4 and 5.
Oct 14 2009 (Red Hat Issues Fix for JBoss) Tomcat Authentication Response Error Lets Remote Users Determine Valid Usernames   (bugzilla@redhat.com)
Red Hat has released a fix for Tomcat6 for JBoss Enterprise Web Server 1.0.0 for Red Hat Enterprise Linux 4 and 5.
Nov 10 2009 (Red Hat Issues Fix) Tomcat Authentication Response Error Lets Remote Users Determine Valid Usernames   (bugzilla@redhat.com)
Red Hat has issued a fix for Red Hat Application Server v2.
Dec 1 2009 (Red Hat Issues Fix for Red Hat Network Satellite Server) Tomcat Authentication Response Error Lets Remote Users Determine Valid Usernames   (bugzilla@redhat.com)
Red Hat has issued a fix for Red Hat Network Satellite Server 5.2 and 5.3.
Nov 24 2010 (HP Issues Fix for HP-UX) Tomcat Authentication Response Error Lets Remote Users Determine Valid Usernames
HP has issued a fix for HP-UX 11.23 and 11.31.



 Source Message Contents

Date:  Thu, 4 Jun 2009 00:03:03 -0400
Subject:  Apache Tomcat


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

CVE-2009-0580: Tomcat information disclosure vulnerability

Severity: Low

Vendor:
The Apache Software Foundation

Versions Affected:
Tomcat 4.1.0 to 4.1.39
Tomcat 5.5.0 to 5.5.27
Tomcat 6.0.0 to 6.0.18

The unsupported Tomcat 3.x, 4.0.x and 5.0.x versions may be also affected.

Description:
Due to insufficient error checking in some authentication classes,
Tomcat allows for the enumeration (brute force testing) of usernames by
supplying illegally URL encoded passwords. The attack is possible if
form based authenticiaton (j_security_check) with one of the following
authentication realms is used:
 * MemoryRealm
 * DataSourceRealm
 * JDBCRealm

Mitigation:
6.0.x users should do one of the following:
 - upgrade to 6.0.20
 - apply this patch http://svn.apache.org/viewvc?rev=747840&view=rev
5.5.x users should do one of the following:
 - upgrade to 5.5.28 when released
 - apply this patch http://svn.apache.org/viewvc?rev=781379&view=rev
4.1.x users should do one of the following:
 - upgrade to 4.1.40 when released
 - apply this patch http://svn.apache.org/viewvc?rev=781382&view=rev

Example:
The following POST request should trigger an error (500 server error or
empty response, depending on the configuration) if the ROOT web
application is configured to use FORM authentication:

POST /j_security_check HTTP/1.1
Host: localhost

j_username=tomcat&j_password=%

Credit:
This issue was discovered by D. Matscheko and T. Hackner of SEC Consult.

References:
http://tomcat.apache.org/security.html

Mark Thomas
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkommckACgkQb7IeiTPGAkP75ACg7XYuld/25X2ltLLTeeQx88UB
pFgAn1f6mIpzU7QUnjF4lsHcR+6lY67B
=a0AC
-----END PGP SIGNATURE-----

 
 


Go to the Top of This SecurityTracker Archive Page





Home   |    View Topics   |    Search   |    Contact Us

Copyright 2014, SecurityGlobal.net LLC