User Attribute Enumeration when Using DaoAuthenticationProvider
Spring Security
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| org.springframework.security:spring-security-core Maven |
|
|
Spring Security
| Product | Affected | Fixed in |
|---|---|---|
| org.springframework.security:spring-security-core Maven |
|
|
Vulnerability in Spring Spring Security. If an application is using the UserDetails#isEnabled, #isAccountNonExpired, or #isAccountNonLocked user attributes, to enable, expire, or lock users, then DaoAuthenticationProvider's timing attack defense can be bypassed for users who are disabled, expired, or locked.This issue affects Spring Security: from 5.7.0 through 5.7.22, from 5.8.0 through 5.8.24, from 6.3.0 through 6.3.15, from 6.5.0 through 6.5.9, from 7.0.0 through 7.0.4.
From the CVE record · vmware
Spring Security’s DaoAuthenticationProvider timing attack defense can be bypassed for disabled, expired, or locked users. This occurs when an application uses UserDetails attributes to disable, expire, or lock accounts. The input does not specify whether authentication or user interaction is required.
Teams using Maven org.springframework.security:spring-security-core in the listed affected 5.7, 5.8, 6.3, 6.4, 6.5, or 7.0 version ranges should check their applications.