Document DaoAuthenticationProvider timing-attack mitigation - #19533
Open
AzazelSensei wants to merge 1 commit into
Open
Document DaoAuthenticationProvider timing-attack mitigation#19533AzazelSensei wants to merge 1 commit into
AzazelSensei wants to merge 1 commit into
Conversation
spring-projects-issues
added
the
status: waiting-for-triage
Note the user-not-found dummy PasswordEncoder path and the mixed-hash limitation in the DaoAuthenticationProvider and exploits docs. Closes spring-projectsgh-19082 Signed-off-by: Abdullah <AzazelSensei@users.noreply.github.com>
AzazelSensei
force-pushed
the
docs/timing-attack-mitigation
branch
from
August 12, 2026 09:02
50e6b65 to
5b2f5ba
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Document that
DaoAuthenticationProvidermitigates username-enumeration timing attacks on the user-not-found path by performing equivalent password-encoding work, and note the limitation when mixedPasswordEncoder/ hash algorithms are in use.Changes are aligned with the current
retrieveUser/mitigateAgainstTimingAttackimplementation.Closes #19082