CVE-2017-1000070
UnknownEPSS 1.00%
Last modified
CVE-2017-1000070 is a vulnerability of currently unknown severity. 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. EPSS estimates a 1.00% chance of exploitation in the next 30 days.
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
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Oauth2 Proxy Project | Oauth2 Proxy | <= 2.1 |
References
- https://github.com/bitly/oauth2_proxy/pull/359Patch, Third Party Advisory
- https://tools.ietf.org/html/rfc6819#section-5.2.3.5Technical Description
- https://github.com/bitly/oauth2_proxy/pull/359Patch, Third Party Advisory
- https://tools.ietf.org/html/rfc6819#section-5.2.3.5Technical Description
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2017-1000070?
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
How severe is CVE-2017-1000070?
Severity scoring for CVE-2017-1000070 is pending analysis. The EPSS model estimates a 1.00% probability of exploitation in the next 30 days.
How do I fix CVE-2017-1000070?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.
Are you affected by CVE-2017-1000070?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST