# CVE-2021-22119: Resource Exhaustion in Spring Security - **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`) - **Exploited in the wild:** Not known - **Fix available:** Yes - **Published:** 29 Jun 2021 - **Updated:** 3 Aug 2024 - **Also known as:** GHSA-w9jg-gvgr-354m ## What is CVE-2021-22119? CVE-2021-22119 is a high-severity vulnerability in Oracle Communications Cloud Native Core Policy, published on 29 Jun 2021. ### Official description 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. Weakness: CWE-863 (Incorrect Authorization), CWE-400 (Uncontrolled Resource Consumption) ## Which versions are affected by CVE-2021-22119? 16 open source packages ship an affected version, including org.springframework.security:spring-security-core and org.springframework.security:spring-security-oauth2-client. It affects 2 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.springframework.security:spring-security-core` | Maven | From 5.2.0 | 5.2.11 | | `org.springframework.security:spring-security-core` | Maven | From 5.2.0 | 5.2.11 | | `org.springframework.security:spring-security-core` | Maven | From 5.3.0 | 5.3.10 | | `org.springframework.security:spring-security-core` | Maven | From 5.3.0 | 5.3.10 | | `org.springframework.security:spring-security-core` | Maven | From 5.4.0 | 5.4.7 | | `org.springframework.security:spring-security-core` | Maven | From 5.4.0 | 5.4.7 | | `org.springframework.security:spring-security-core` | Maven | From 5.5.0 | 5.5.1 | | `org.springframework.security:spring-security-core` | Maven | From 5.5.0 | 5.5.1 | | `org.springframework.security:spring-security-oauth2-client` | Maven | From 5.2.0 | 5.2.11 | | `org.springframework.security:spring-security-oauth2-client` | Maven | From 5.2.0 | 5.2.11 | | `org.springframework.security:spring-security-oauth2-client` | Maven | From 5.3.0 | 5.3.10 | | `org.springframework.security:spring-security-oauth2-client` | Maven | From 5.3.0 | 5.3.10 | | `org.springframework.security:spring-security-oauth2-client` | Maven | From 5.4.0 | 5.4.7 | | `org.springframework.security:spring-security-oauth2-client` | Maven | From 5.4.0 | 5.4.7 | | `org.springframework.security:spring-security-oauth2-client` | Maven | From 5.5.0 | 5.5.1 | | `org.springframework.security:spring-security-oauth2-client` | Maven | From 5.5.0 | 5.5.1 | Products: Oracle Communications Cloud Native Core Policy, Vmware Spring Security. ## How do I fix CVE-2021-22119? Upgrade org.springframework.security:spring-security-core to a fixed version for your release line: 5.2.11, 5.3.10, 5.4.7 or 5.5.1. ## Is CVE-2021-22119 being exploited? There is no known exploitation of CVE-2021-22119 in the wild and no public exploit code. Public exploit code: - Applications that reproduce CVE-2021-22119 (github_poc): https://github.com/mari6274/oauth-client-exploit ## Other vulnerabilities in Oracle Communications Cloud Native Core Policy - [CVE-2021-35574](https://insights.sbomify.com/CVE-2021-35574/): Denial of service in Outside In Technology (high 7.5) - [CVE-2021-23440](https://insights.sbomify.com/CVE-2021-23440/): Prototype Pollution (high 7.3) - [CVE-2019-3799](https://insights.sbomify.com/CVE-2019-3799/): Directory Traversal with spring-cloud-config-server (medium 6.5) - [CVE-2021-33880](https://insights.sbomify.com/CVE-2021-33880/): Observable Timing Discrepancy in aaugustin websockets library (medium 5.9) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2021-22119 and fix it if it is affected. What it is: CVE-2021-22119 is a high-severity vulnerability in Oracle Communications Cloud Native Core Policy, published on 29 Jun 2021. Exploitation: There is no known exploitation of CVE-2021-22119 in the wild and no public exploit code. Affected packages and fixed versions: - org.springframework.security:spring-security-core (Maven): affected from 5.2.0; fixed in 5.2.11 - org.springframework.security:spring-security-core (Maven): affected from 5.2.0; fixed in 5.2.11 - org.springframework.security:spring-security-core (Maven): affected from 5.3.0; fixed in 5.3.10 - org.springframework.security:spring-security-core (Maven): affected from 5.3.0; fixed in 5.3.10 - org.springframework.security:spring-security-core (Maven): affected from 5.4.0; fixed in 5.4.7 - org.springframework.security:spring-security-core (Maven): affected from 5.4.0; fixed in 5.4.7 - org.springframework.security:spring-security-core (Maven): affected from 5.5.0; fixed in 5.5.1 - org.springframework.security:spring-security-core (Maven): affected from 5.5.0; fixed in 5.5.1 - org.springframework.security:spring-security-oauth2-client (Maven): affected from 5.2.0; fixed in 5.2.11 - org.springframework.security:spring-security-oauth2-client (Maven): affected from 5.2.0; fixed in 5.2.11 - org.springframework.security:spring-security-oauth2-client (Maven): affected from 5.3.0; fixed in 5.3.10 - org.springframework.security:spring-security-oauth2-client (Maven): affected from 5.3.0; fixed in 5.3.10 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2021-22119/ (Markdown: https://insights.sbomify.com/CVE-2021-22119/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2021-22119 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-22119 - OSV: https://osv.dev/vulnerability/CVE-2021-22119 --- From sbomify Insights: https://insights.sbomify.com/CVE-2021-22119/ Summaries are generated and may contain mistakes; the official description above is the record.