A weakness has been reported in Spring Security, which can be exploited by malicious people to determine valid usernames.
The weakness is caused due to the DaoAuthenticationProvider component displaying messages at different speeds depending on whether an unsuccessful login attempt is performed with a valid or invalid username.
The weakness is reported in versions 3.1.0 through 3.1.2, 3.0.0 through 3.0.7, and 2.0.0 through 2.0.7.
Solution: Update to versions 3.1.3, 3.0.8, or 2.0.8.
Provided and/or discovered by: The vendor credits Nicholas Goodwin.
Original Advisory: http://support.springsource.com/security/cve-2012-5055
Do you have additional information related to this advisory?
Please provide information about patches, mitigating factors, new versions, exploits, faulty patches, links, and other relevant data by posting comments to this Advisory. You can also send this
information to firstname.lastname@example.org
Subject: Spring Security DaoAuthenticationProvider Username Enumeration Weakness
No posts yet
You must be logged in to post a comment.
Secunia Customer Login
Not a customer already?
Learn more about how our market leading Vulnerability Management solutions can help you manage risk and ensure compliance.