GHSA-w9jg-gvgr-354m
HIGHGHSA-w9jg-gvgr-354m is a high-severity (CVSS 7.5) Uncontrolled Resource Consumption vulnerability in org.springframework.security:spring-security-core. O3 Security confirms whether GHSA-w9jg-gvgr-354m is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Resource Exhaustion in Spring Security
Blast Radius
org.springframework.security:spring-security-core☕org.springframework.security:spring-security-core☕org.springframework.security:spring-security-core☕org.springframework.security:spring-security-core☕org.springframework.security:spring-security-oauth2-client☕org.springframework.security:spring-security-oauth2-client☕org.springframework.security:spring-security-oauth2-client☕org.springframework.security:spring-security-oauth2-clientReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.springframework.security:spring-security-core | ≥ 5.5.0&&< 5.5.1 | 5.5.1 |
| ☕Maven | org.springframework.security:spring-security-core | ≥ 5.4.0&&< 5.4.7 | 5.4.7 |
| ☕Maven | org.springframework.security:spring-security-core | ≥ 5.3.0&&< 5.3.10 | 5.3.10 |
| ☕Maven | org.springframework.security:spring-security-core | ≥ 5.2.0&&< 5.2.11 | 5.2.11 |
| ☕Maven | org.springframework.security:spring-security-oauth2-client | ≥ 5.5.0&&< 5.5.1 | 5.5.1 |
| ☕Maven | org.springframework.security:spring-security-oauth2-client | ≥ 5.4.0&&< 5.4.7 | 5.4.7 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework.security:spring-security-core. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update org.springframework.security:spring-security-core to 5.5.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-w9jg-gvgr-354m is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-w9jg-gvgr-354m is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-w9jg-gvgr-354m. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-w9jg-gvgr-354m in your dependencies?
O3 detects GHSA-w9jg-gvgr-354m across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.