First published: Wed Dec 05 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.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
VMware Spring Security | <=2.0.6 | |
VMware Spring Security | =2.0.0 | |
VMware Spring Security | =2.0.1 | |
VMware Spring Security | =2.0.2 | |
VMware Spring Security | =2.0.3 | |
VMware Spring Security | =2.0.4 | |
VMware Spring Security | =2.0.5 | |
VMware Spring Security | =3.0.0 | |
VMware Spring Security | =3.0.1 | |
VMware Spring Security | =3.0.2 | |
VMware Spring Security | =3.0.3 | |
VMware Spring Security | =3.0.4 | |
VMware Spring Security | =3.0.5 | |
VMware Spring Security | =3.1.1 | |
VMware Spring Security | =3.1.2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2012-5055 is considered a vulnerability that could allow information disclosure through username enumeration.
To fix CVE-2012-5055, upgrade VMware SpringSource Spring Security to version 2.0.8, 3.0.8, or 3.1.3 and later.
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.
The potential consequences of CVE-2012-5055 include an increased risk of unauthorized access due to username enumeration.
There are no official workarounds for CVE-2012-5055; the recommended action is to update to a patched version.