CVE-2017-1000069 Cross-site Request Forgery (CSRF)
High 8.8
Published
Updated
Check this codebase for CVE-2017-1000069 and fix it if it is affected.
What it is: CVE-2017-1000069 is a high-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.
Exploitation: There is no known exploitation of CVE-2017-1000069 in the wild and no public exploit code.
Affected packages and fixed versions:
- github.com/bitly/oauth2_proxy (Go): affected all versions; fixed in 2.2.0
- github.com/bitly/oauth2_proxy (Go): affected all versions; fixed in 2.2.0
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2017-1000069/ (Markdown: https://insights.sbomify.com/CVE-2017-1000069/index.md)
Cross-site request forgery in Bitly oauth2_proxy allows attackers to hijack user sessions during authentication.
- 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-1000069?
CVE-2017-1000069 is a high-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
CSRF in Bitly oauth2_proxy 2.1 during authentication flow
Weakness: CWE-352
Which versions are affected by CVE-2017-1000069?
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-1000069?
Upgrade github.com/bitly/oauth2_proxy to 2.2.0 or later.
Is CVE-2017-1000069 being exploited?
There is no known exploitation of CVE-2017-1000069 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-2026-41059 OAuth2 Proxy has an Authentication Bypass via Fragment Confusion in skip_auth_routes and skip_auth_regex
- CVE-2020-11053 Open Redirect in OAuth2 Proxy
Sources
Also known as GHSA-rrm8-32g4-w8m3.