User Attribute Enumeration when Using DaoAuthenticationProvider
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.5.10, 7.0.5
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Spring 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
- org.springframework.security:spring-security-coreMaven
From 5.7.0 · through 5.7.22
- org.springframework.security:spring-security-coreMaven
From 5.8.0 · through 5.8.24
- org.springframework.security:spring-security-coreMaven
From 6.3.0 · through 6.3.15
- org.springframework.security:spring-security-coreMaven
From 6.4.0 · through 6.4.15
- org.springframework.security:spring-security-coreMaven
From 6.5.0 · fixed in 6.5.10
- org.springframework.security:spring-security-coreMaven
From 7.0.0 · fixed in 7.0.5