{"answers":{"affected":"2 open source packages ship an affected version, including github.com/bitly/oauth2_proxy. It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-1000070 in the wild and no public exploit code.","fix":"Upgrade github.com/bitly/oauth2_proxy to 2.2.0 or later.","what":"CVE-2017-1000070 is a medium-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."},"fix_prompt":"Check this codebase for CVE-2017-1000070 and fix it if it is affected.\n\nWhat it is: CVE-2017-1000070 is a medium-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.\nExploitation: There is no known exploitation of CVE-2017-1000070 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/bitly/oauth2_proxy (Go): affected all versions; fixed in 2.2.0\n- github.com/bitly/oauth2_proxy (Go): affected all versions; fixed in 2.2.0\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2017-1000070/ (Markdown: https://insights.sbomify.com/CVE-2017-1000070/index.md)","id":"CVE-2017-1000070","markdown":"https://insights.sbomify.com/CVE-2017-1000070/index.md","name":"CVE-2017-1000070","record":{"aliases":["GHSA-jm34-xm8m-w958"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"OAuth2 proxy","requires_auth":"none","summary":"An open redirect in the OAuth2 flow allows attackers to redirect users to malicious sites, potentially facilitating phishing or token theft.","user_interaction":"required","vuln_class":"open_redirect"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"oauth2_proxy","vendor":"oauth2_proxy_project"}],"cvss":{"score":6.1,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N","version":"3.0"},"cwes":[{"id":"CWE-601","name":"URL Redirection to Untrusted Site"}],"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","ecosystems":["Go"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Open Redirect in oauth2_proxy","id":"CVE-2017-1000070","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"open_redirect","year":"2017"},"n_packages":2,"n_references":2,"next":{"headline":"Auth bypass in n/a","id":"CVE-2017-1000071"},"packages":[{"ecosystem":"Go","fixed":["2.2.0"],"introduced":["0"],"last_affected":[],"package":"github.com/bitly/oauth2_proxy","purl":null,"source":"GHSA-jm34-xm8m-w958"},{"ecosystem":"Go","fixed":["2.2.0"],"introduced":["0"],"last_affected":[],"package":"github.com/bitly/oauth2_proxy","purl":"pkg:golang/github.com/bitly/oauth2_proxy","source":"GHSA-jm34-xm8m-w958"}],"prev":{"headline":"Cross-site Request Forgery (CSRF)","id":"CVE-2017-1000069"},"products":["n/a"],"published":"2017-07-13","related":[{"cvss_score":9.1,"headline":"OAuth2 Proxy has an Authentication Bypass via X-Forwarded-Uri Header Spoofing","id":"CVE-2026-40575","kev_date_added":null,"published":"2026-04-21"},{"cvss_score":9.1,"headline":"OAuth2 Proxy: Health Check User-Agent Matching Bypasses Authentication in auth_request Mode","id":"CVE-2026-34457","kev_date_added":null,"published":"2026-04-14"},{"cvss_score":9.1,"headline":"OAuth2-Proxy has authentication bypass in oauth2-proxy skip_auth_routes due to Query Parameter inclusion","id":"CVE-2025-54576","kev_date_added":null,"published":"2025-07-30"},{"cvss_score":8.8,"headline":"Cross-site Request Forgery (CSRF)","id":"CVE-2017-1000069","kev_date_added":null,"published":"2017-07-13"},{"cvss_score":8.2,"headline":"OAuth2 Proxy has an Authentication Bypass via Fragment Confusion in skip_auth_routes and skip_auth_regex","id":"CVE-2026-41059","kev_date_added":null,"published":"2026-04-21"},{"cvss_score":7.1,"headline":"Open Redirect in OAuth2 Proxy","id":"CVE-2020-11053","kev_date_added":null,"published":"2020-05-07"},{"cvss_score":6.8,"headline":"OAuth2 Proxy has an Authorization Bypass in Email Domain Validation via Malformed Multi-@ Email Claims","id":"CVE-2026-40574","kev_date_added":null,"published":"2026-04-21"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"An open redirect in the OAuth2 flow allows attackers to redirect users to malicious sites, potentially facilitating phishing or token theft.","url":"https://insights.sbomify.com/CVE-2017-1000070/"}