Get ahead
VMware offers training and certification to turbo-charge your progress.
Learn moreSpring Security's reactive authentication support, AbstractUserDetailsReactiveAuthenticationManager and UserDetailsRepositoryReactiveAuthenticationManager, do not invoke the configured PasswordEncoder when a submitted username cannot be found, unlike its blocking counterpart DaoAuthenticationProvider.
Because password encoding is deliberately CPU-intensive, the response time for a nonexistent username is measurably shorter than for a valid username with an incorrect password.
Preconditions:
AbstractUserDetailsReactiveAuthenticationManager or a subclass, such as UserDetailsRepositoryReactiveAuthenticationManager (used by reactive .formLogin()).An unauthenticated attacker who can measure authentication response times can use this difference to enumerate valid usernames.
Spring Security:
| Fix version | Availability |
|---|---|
| 7.1.3 | OSS |
| 7.1.2.1 | Enterprise Support Only |
| 7.0.9 | OSS |
| 7.0.8.1 | Enterprise Support Only |
| 6.5.13 | Enterprise Support Only |
| 6.4.20 | Enterprise Support Only |
| 5.8.29 | Enterprise Support Only |
| 5.7.27 | Enterprise Support Only |
No further mitigation steps are necessary.
To report a security vulnerability for a project within the Spring portfolio, see the Security Policy