CVE-2017-1000070 Open Redirect in oauth2_proxy
An open redirect in the OAuth2 flow allows attackers to redirect users to malicious sites, potentially facilitating phishing or token theft.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- Available
What is CVE-2017-1000070?
CVE-2017-1000070 is a medium-severity vulnerability in n/a, published on 13 Jul 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Official description
The Bitly oauth2_proxy in version 2.1 and earlier was affected by an open redirect vulnerability during the start and termination of the 2-legged OAuth flow. This issue was caused by improper input validation and a violation of RFC-6819
Weakness: CWE-601
Which versions are affected by CVE-2017-1000070?
2 open source packages ship an affected version, including github.com/bitly/oauth2_proxy. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
github.com/bitly/oauth2_proxy Go | All versions | 2.2.0 |
github.com/bitly/oauth2_proxy Go | All versions | 2.2.0 |
Products include Oauth2 Proxy Project Oauth2 Proxy.
How do I fix CVE-2017-1000070?
Upgrade github.com/bitly/oauth2_proxy to 2.2.0 or later.
Is CVE-2017-1000070 being exploited?
There is no known exploitation of CVE-2017-1000070 in the wild and no public exploit code.
Other vulnerabilities in n/a
- CVE-2026-40575 OAuth2 Proxy has an Authentication Bypass via X-Forwarded-Uri Header Spoofing
- CVE-2026-34457 OAuth2 Proxy: Health Check User-Agent Matching Bypasses Authentication in auth_request Mode
- CVE-2025-54576 OAuth2-Proxy has authentication bypass in oauth2-proxy skip_auth_routes due to Query Parameter inclusion
- CVE-2017-1000069 Cross-site Request Forgery (CSRF)
- CVE-2026-41059 OAuth2 Proxy has an Authentication Bypass via Fragment Confusion in skip_auth_routes and skip_auth_regex
Sources
Also known as GHSA-jm34-xm8m-w958.