Skip to content

GHSA-vqxh-445g-37fc CVE-2025-22234

Spring Security has a broken timing attack mitigation implemented in DaoAuthenticationProvide

Medium Maven
Severity
5.3 / 10
Medium · CVSS 3.1
Exploit chance (EPSS)
0.39%
Chance of exploitation in the next 30 days. Higher than 33.19% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-208 Observable Timing Discrepancy
Fix
6.3.9
Upgrade org.springframework.security:spring-security-core to this version or later

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.

Affected versions

Maven

PackageVulnerableFixed in
org.springframework.security:spring-security-core
>= 6.3.8, < 6.3.9
6.3.9
org.springframework.security:spring-security-core
>= 6.4.4, < 6.4.5
6.4.5

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

org.springframework.security:spring-security-core Maven → 6.3.9

maven
<dependency><groupId>org.springframework.security</groupId><artifactId>spring-security-core</artifactId><version>6.3.9</version></dependency>
gradle
implementation("org.springframework.security:spring-security-core:6.3.9")

Severity breakdown

CVSS 3.1 5.3

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

Weakness

CWE-208: Observable Timing Discrepancy

Two separate operations in a product require different amounts of time to complete, in a way that is observable to an actor and reveals security-relevant information about the state of the product, such as whether a particular operation was successful or not.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-vxf7-qj7q-83fh
Spring Security Vulnerable to User Attribute Enumeration when Using DaoAuthenticationProvider
Low Also affects org.springframework.security:spring-security-core
GHSA-x2wq-9x2f-fhj7
Spring Security Core has a TOCTOU race condition when One-Time Token login with JdbcOneTimeTokenService is configured
Medium Also affects org.springframework.security:spring-security-core
GHSA-8v5q-rhf3-jphm
Spring Security annotation detection mechanism has authorization bypass
High Also affects org.springframework.security:spring-security-core
GHSA-9pp5-9c7g-4r83
Spring Security authorization bypass for method security annotations on private methods
Critical Also affects org.springframework.security:spring-security-core
GHSA-hh3m-g4qj-4835
Spring Security Vulnerable to Authorization Bypass via Security Annotations
Medium Also affects org.springframework.security:spring-security-core
GHSA-q3v6-hm2v-pw99
Spring Framework has Authorization Bypass for Case Sensitive Comparisons
Medium Also affects org.springframework.security:spring-security-core
GHSA-hmqf-wpq9-jq83
Spring Security Missing Authorization vulnerability
High Also affects org.springframework.security:spring-security-core
GHSA-f3jh-qvm4-mg39
Erroneous authentication pass in Spring Security
High Also affects org.springframework.security:spring-security-core
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor