CVE-2017-1000070 json
Open Redirect in oauth2_proxy
published 9y ago modified 4mo ago also GHSA-jm34-xm8m-w958 , EUVD-2021-2545
- cvss
- 6.1
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.0%
- EPSS 1.0% chance of exploitation in 30 days, percentile 62%
- public exploits
- 0
- none known
Summary
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
Patch / fix
- go github.com/bitly/oauth2_proxy 2.2.0
- github.com/bitly/oauth2_proxy@289a6cc commit
- github.com/bitly/oauth2_proxy#359 pull request
Is CVE-2017-1000070 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
1.00% chance of exploitation in the next 30 days, higher than 62% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 6.1 | CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N |
| NVD | 2.0 | 5.8 | AV:N/AC:M/Au:N/C:P/I:P/A:N |
| GitHub | 3.0 | 6.1 | CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/bitly/oauth2_proxy | <2.2.0 |
2.2.0 |
Classification
- Weakness
-
- CWE-601 URL Redirection to Untrusted Site
References
-
github.com
/bitly/oauth2_proxy/pull/359
web, patch, third-party-advisory
-
github.com
/bitly/oauth2_proxy/commit/289a6ccf463a425c7606178c510fc5eeb9c8b050
web
-
tools.ietf.org
/html/rfc6819#section-5.2.3.5
web, technical-description
-
nvd.nist.gov
/vuln/detail/CVE-2017-1000070
advisory
-
github.com
/bitly/oauth2_proxy/issues/228
web
-
web.nvd.nist.gov
/view/vuln/detail?vulnId=CVE-2017-1000070
web
Sources
- CVE List CVE-2017-1000070
- GitHub Advisory GHSA-jm34-xm8m-w958
- NVD CVE-2017-1000070
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.