GHSA-rrpm-pj7p-7j9q
CRITICALGHSA-rrpm-pj7p-7j9q is a critical-severity (CVSS 9.8) Code Injection vulnerability in org.springframework.security.oauth:spring-security-oauth2. O3 Security confirms whether GHSA-rrpm-pj7p-7j9q is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Spring Security OAuth vulnerable to remote code execution (RCE)
Blast Radius
org.springframework.security.oauth:spring-security-oauth2☕org.springframework.security.oauth:spring-security-oauth2☕org.springframework.security.oauth:spring-security-oauth2☕org.springframework.security.oauth:spring-security-oauth2☕org.springframework.security.oauth:spring-security-oauth2Real-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 OAuth versions prior to 2.3.3, prior to 2.2.2, prior to 2.1.2, and prior to 2.0.15 contain a remote code execution vulnerability. An attacker can craft an authorization request to the authorization endpoint that can lead to remote code execution when the resource owner is forwarded to the approval endpoint.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.springframework.security.oauth:spring-security-oauth2 | ≥ 2.3.0&&< 2.3.3 | 2.3.3 |
| ☕Maven | org.springframework.security.oauth:spring-security-oauth2 | ≥ 2.2.0&&< 2.2.2 | 2.2.2 |
| ☕Maven | org.springframework.security.oauth:spring-security-oauth2 | ≥ 2.1.0&&< 2.1.2 | 2.1.2 |
| ☕Maven | org.springframework.security.oauth:spring-security-oauth2 | ≥ 2.0.0&&< 2.0.15 | 2.0.15 |
| ☕Maven | org.springframework.security.oauth:spring-security-oauth2 | ≥ 1.0.0 | No fix |
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.oauth:spring-security-oauth2. 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.oauth:spring-security-oauth2 to 2.3.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rrpm-pj7p-7j9q 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-rrpm-pj7p-7j9q 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-rrpm-pj7p-7j9q. 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-rrpm-pj7p-7j9q in your dependencies?
O3 detects GHSA-rrpm-pj7p-7j9q across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.