CVE-2020-4037GHSA-5M6C-JP6F-2VCVBIT-OAUTH2-PROXY-2020-4037
Open Redirect in OAuth2 Proxy
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.0.0
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
In OAuth2 Proxy from version 5.1.1 and less than version 6.0.0, users can provide a redirect address for the proxy to send the authenticated user to at the end of the authentication flow. This is expected to be the original URL that the user was trying to access. This redirect URL is checked within the proxy and validated before redirecting the user to prevent malicious actors providing redirects to potentially harmful sites. This has been fixed in version 6.0.0.
Timeline
- CVE published
- Record last updated
Affected versions
- OAuth2 Proxy OAuth2 Proxy
From 5.1.1 · fixed in 6.0.0
- github.com/oauth2-proxy/oauth2-proxyGo
From 5.1.1 · fixed in 6.0.0