CVE-2017-1000069
Cross-site Request Forgery (CSRF)
CSRF in Bitly oauth2_proxy 2.1 during authentication flow
Attack profile
How easy it is to exploit
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- Required
What an attacker can affect
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Exploit likelihood
What each source reports
NVD Score used
CSRF in Bitly oauth2_proxy 2.1 during authentication flow
- Record
CVE-2017-1000069- CVSS 3.0
- 8.8 High
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H - CVSS 2.0
- 6.8 Medium
AV:N/AC:M/Au:N/C:P/I:P/A:P - Weakness
- CWE-352
- Updated
- 2026-11-02
CVE List No score
CSRF in Bitly oauth2_proxy 2.1 during authentication flow
- Record
CVE-2017-1000069- Updated
- 2026-11-02
EUVDEUVD-2021-2584 No score
CSRF in Bitly oauth2_proxy 2.1 during authentication flow
- Record
EUVD-2021-2584- Updated
- 2026-11-03
GitHub AdvisoriesGHSA-rrm8-32g4-w8m3
Cross-site Request Forgery (CSRF)
CSRF in Bitly oauth2_proxy 2.1 during authentication flow
- Record
GHSA-rrm8-32g4-w8m3- CVSS 3.1
- 8.8 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H - Weakness
- CWE-352
- Updated
- 2026-11-02
OSV
CSRF in Bitly oauth2_proxy 2.1 during authentication flow
- Record
CVE-2017-1000069- CVSS 3.0
- 8.8 High
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H - Updated
- 2026-11-02
OSVGHSA-rrm8-32g4-w8m3
Cross-site Request Forgery (CSRF)
CSRF in Bitly oauth2_proxy 2.1 during authentication flow
- Record
GHSA-rrm8-32g4-w8m3- CVSS 3.1
- 8.8 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H - Weakness
- CWE-352
- Updated
- 2026-11-02
Affected products
Affected packages
| Package | Affected | Fixed |
|---|---|---|
github.com/bitly/oauth2_proxyGo |
before 2.2.0 | 2.2.0 |
History
| Recorded | Changed | Sources |
|---|---|---|
| aliases | EUVD | |
| first indexed | CVE List, GitHub Advisories, NVD, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2017-1000069 is a high vulnerability (CVSS 8.8) in Oauth2 Proxy Project Proxy, published July 13, 2017. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 0.74%, the 54th percentile. Fixed in github.com/bitly/oauth2_proxy 2.2.0.