Spring Security - BCrypt Password Encoder maximum password length breaks timing attack mitigation
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Spring | Spring Security | affected |
|
No data.
No data.
| Vendor | Product | Versions |
|---|---|---|
| Spring | Spring | — |
Vendor Solution
Upgrade to a fixed version: 5.7.17, 5.8.19, 6.0.17, 6.1.15, 6.2.11, 6.3.9, or 6.4.5 (depending on your release line).
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-vqxh-445g-37fc | Spring Security has a broken timing attack mitigation implemented in DaoAuthenticationProvide |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.390% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| References |
| |
| Metrics |
threat_severity
|
threat_severity
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Spring
Spring spring |
|
| Vendors & Products |
Spring
Spring spring |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | The fix applied in CVE-2025-22228 inadvertently broke the timing attack mitigation implemented in DaoAuthenticationProvider. This can allow attackers to infer valid usernames or other authentication behavior via response-time differences under certain configurations. | |
| Title | Spring Security - BCrypt Password Encoder maximum password length breaks timing attack mitigation | |
| Weaknesses | CWE-208 | |
| References |
| |
| Metrics |
cvssV3_1
|