GHSA-mmf6-6597-3v6m
MEDIUMGHSA-mmf6-6597-3v6m is a medium-severity (CVSS 5.4) Open Redirect vulnerability in org.springframework.security.oauth:spring-security-oauth. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether GHSA-mmf6-6597-3v6m is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Open Redirect in Spring Security OAuth
Blast Radius
org.springframework.security.oauth:spring-security-oauth☕org.springframework.security.oauth:spring-security-oauth☕org.springframework.security.oauth:spring-security-oauth☕org.springframework.security.oauth:spring-security-oauthReal-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 2.3 prior to 2.3.6, 2.2 prior to 2.2.5, 2.1 prior to 2.1.5, and 2.0 prior to 2.0.18, as well as older unsupported versions could be susceptible to an open redirector attack that can leak an authorization code. A malicious user or attacker can craft a request to the authorization endpoint using the authorization code grant type, and specify a manipulated redirection URI via the redirect_uri parameter. This can cause the authorization server to redirect the resource owner user-agent to a URI under the control of the attacker with the leaked authorization code.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.springframework.security.oauth:spring-security-oauth | ≥ 2.0.0.RELEASE&&< 2.0.18.RELEASE | 2.0.18.RELEASE |
| ☕Maven | org.springframework.security.oauth:spring-security-oauth | ≥ 2.1.0.RELEASE&&< 2.1.5.RELEASE | 2.1.5.RELEASE |
| ☕Maven | org.springframework.security.oauth:spring-security-oauth | ≥ 2.2.0.RELEASE&&< 2.2.5.RELEASE | 2.2.5.RELEASE |
| ☕Maven | org.springframework.security.oauth:spring-security-oauth | ≥ 2.3.0.RELEASE&&< 2.3.6.RELEASE | 2.3.6.RELEASE |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Spring Security OAuth - Open Redirector
by Riemann · Jun 17, 2019
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-oauth. 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-oauth to 2.0.18.RELEASE or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mmf6-6597-3v6m 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-mmf6-6597-3v6m 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-mmf6-6597-3v6m. 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-mmf6-6597-3v6m in your dependencies?
O3 detects GHSA-mmf6-6597-3v6m across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.