CVE-2017-1000069: CSRF

Published Jul 13, 2017
·
Updated

CSRF in Bitly oauth2proxy 2.1 during authentication flow

Affected Software

2 affected componentsFixes available
go/github.com/bitly/oauth2_proxy<2.2.0
2.2.0
Oauth2 Proxy Project Oauth2 Proxy=2.1

Event History

Jul 13, 2017
CVE Published
via MITRE·08:00 PM
Data Sourced
via MITRE·08:00 PM
Description
Dec 20, 2021
Advisory Published
06:04 PM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2017-1000069?

CVE-2017-1000069 has a severity level classified as medium, indicating a moderate risk to systems.

2

How do I fix CVE-2017-1000069?

To fix CVE-2017-1000069, upgrade to oauth2_proxy version 2.2.0 or later.

3

Which versions of oauth2_proxy are affected by CVE-2017-1000069?

CVE-2017-1000069 affects oauth2_proxy version 2.1 and earlier.

4

What kind of vulnerability is CVE-2017-1000069?

CVE-2017-1000069 is a Cross-Site Request Forgery (CSRF) vulnerability occurring during the authentication flow.

5

Who is impacted by CVE-2017-1000069?

Users of oauth2_proxy version 2.1 or earlier are impacted by CVE-2017-1000069.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203