Skip to content
Fencer Intel
medium 6.5

CVE-2022-22969 json

Denial of service in Spring Security OAuth2

published 4y ago modified 4mo ago also GHSA-c2cp-3xj9-97w9 , EUVD-2022-1699

cvss
6.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.3%
EPSS 1.3% chance of exploitation in 30 days, percentile 69%
public exploits
0
none known

Summary

<Issue 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.

Patch / fix

  • maven org.springframework.security.oauth:spring-security-oauth2 2.4.2.RELEASE, 2.5.2.RELEASE
  • pivotal spring_security_oauth 2.4.2, 2.5.2

Is CVE-2022-22969 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

1.25% chance of exploitation in the next 30 days, higher than 69% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
NVD 2.0 4.0 AV:N/AC:L/Au:S/C:N/I:N/A:P
GitHub 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Affected packages

ecosystem package affected fixed in
maven org.springframework.security.oauth:spring-security-oauth2
>=2.5.0.RELEASE, <2.5.2.RELEASE
>=2.4.0.RELEASE, <2.4.2.RELEASE
2.5.2.RELEASE
2.4.2.RELEASE

Affected products

  • n/a Spring Security OAuth

Classification

Weakness
  • CWE-400 Uncontrolled Resource Consumption
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.