Resource Exhaustion in Spring Security
Spring Security
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| org.springframework.security:spring-security-core Maven |
|
|
Spring Security
| Product | Affected | Fixed in |
|---|---|---|
| org.springframework.security:spring-security-core Maven |
|
|
| org.springframework.security:spring-security-oauth2-client Maven |
|
|
Spring Security versions 5.5.x prior to 5.5.1, 5.4.x prior to 5.4.7, 5.3.x prior to 5.3.10 and 5.2.x prior to 5.2.11 are susceptible to a Denial-of-Service (DoS) attack via the initiation of the Authorization Request in an OAuth 2.0 Client Web and WebFlux application. A malicious user or attacker can send multiple requests initiating the Authorization Request for the Authorization Code Grant, which has the potential of exhausting system resources using a single session or multiple sessions.
From the CVE record · vmware
Spring Security OAuth 2.0 Client Web and WebFlux applications are vulnerable when initiating Authorization Code Grant requests. An attacker can send repeated authorization requests through a single session or multiple sessions, potentially exhausting system resources. The input does not specify whether authentication or user interaction is required.
Teams using Maven spring-security-core or spring-security-oauth2-client in Spring Security 5.5.x before 5.5.1, 5.4.x before 5.4.7, 5.3.x before 5.3.10, or 5.2.x before 5.2.11 should check their deployments.