Skip to content

Denial of service in Spring Security OAuth2

Moderate severity GitHub Reviewed Published Apr 22, 2022 to the GitHub Advisory Database • Updated May 14, 2024

Package

maven org.springframework.security.oauth:spring-security-oauth2 (Maven)

Affected versions

>= 2.5.0.RELEASE, < 2.5.2.RELEASE
>= 2.4.0.RELEASE, < 2.4.2.RELEASE

Patched versions

2.5.2.RELEASE
2.4.2.RELEASE

Description

Spring Security OAuth versions 2.5.x prior to 2.5.2 and older unsupported versions are susceptible to a Denial-of-Service (DoS) attack via the initiation of the Authorization Request in an OAuth 2.0 Client 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. This vulnerability exposes OAuth 2.0 Client applications only.

References

Published by the National Vulnerability Database Apr 21, 2022
Published to the GitHub Advisory Database Apr 22, 2022
Reviewed Apr 26, 2022
Last updated May 14, 2024

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

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

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

EPSS score

0.081%
(35th percentile)

Weaknesses

CVE ID

CVE-2022-22969

GHSA ID

GHSA-c2cp-3xj9-97w9

Source code

No known source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.