CVE-2012-5055: Infoleak

Published Dec 5, 2012
·
Updated

DaoAuthenticationProvider in VMware SpringSource Spring Security before 2.0.8, 3.0.x before 3.0.8, and 3.1.x before 3.1.3 does not check the password if the user is not found, which makes the response delay shorter and might allow remote attackers to enumerate valid usernames via a series of login requests.

Affected Software

17 affected components
VMware SpringSource Spring Security<=2.0.6
VMware SpringSource Spring Security=2.0.0
VMware SpringSource Spring Security=2.0.1
VMware SpringSource Spring Security=2.0.2
VMware SpringSource Spring Security=2.0.3
VMware SpringSource Spring Security=2.0.4
VMware SpringSource Spring Security=2.0.5
VMware SpringSource Spring Security=3.0.0
VMware SpringSource Spring Security=3.0.1
VMware SpringSource Spring Security=3.0.2
VMware SpringSource Spring Security=3.0.3
VMware SpringSource Spring Security=3.0.4
VMware SpringSource Spring Security=3.0.5
VMware SpringSource Spring Security=3.1.1
VMware SpringSource Spring Security=3.1.2
IBM Engineering Requirements Management DOORS and DOORS Web Access<=9.7.2.1 - 9.7.2.11
IBM Engineering Requirements Management DOORS and DOORS Web Access<=9.6.1.1 - 9.6.1.13

Event History

Dec 5, 2012
CVE Published
via MITRE·05:00 PM
Data Sourced
via MITRE·05:00 PM
Description
Jul 6, 2026
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2012-5055?

CVE-2012-5055 is considered a vulnerability that could allow information disclosure through username enumeration.

2

How do I fix CVE-2012-5055?

To fix CVE-2012-5055, upgrade VMware SpringSource Spring Security to version 2.0.8, 3.0.8, or 3.1.3 and later.

3

What versions of Spring Security are affected by CVE-2012-5055?

CVE-2012-5055 affects versions of VMware SpringSource Spring Security before 2.0.8, 3.0.x before 3.0.8, and 3.1.x before 3.1.3.

4

What are the potential consequences of CVE-2012-5055?

The potential consequences of CVE-2012-5055 include an increased risk of unauthorized access due to username enumeration.

5

Is there a workaround for CVE-2012-5055?

There are no official workarounds for CVE-2012-5055; the recommended action is to update to a patched version.

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