How severe is CVE-2017-1000070?

CVE-2017-1000070 has a CVSS score of 6.1/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2017-1000070?

CVE-2017-1000070 affects the following packages: github.com/bitly/oauth2_proxy (Go). Ecosystems affected: Go.

How do I fix CVE-2017-1000070?

Update github.com/bitly/oauth2_proxy to 2.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-1000070 is resolved across your whole dependency graph.

How do I detect CVE-2017-1000070 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/bitly/oauth2_proxy, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2017-1000070 if there is no patch (or I can't update yet)?

Stop reflecting attacker-controlled destinations: resolve every redirect target against an allowlist of paths or hosts you own, prefer a server-side key over a full URL in the request, and reject absolute URLs entirely where the flow only ever needs a relative one.

Is CVE-2017-1000070 actively exploited in the wild?

No public exploit code has been indexed for CVE-2017-1000070 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2017-1000070?

CVE-2017-1000070 has an EPSS (Exploit Prediction Scoring System) score of 1.0%, placing it in the 62th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2017-1000070?

CVE-2017-1000070 is classified as Open Redirect (CWE-601). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2017-1000070 published, and has it been updated?

CVE-2017-1000070 was published on July 17, 2017 and was last updated on July 8, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹

🐹 Go

Not in CISA KEV

MEDIUM severity

CVE-2017-1000070 — oauth2_proxy

MEDIUMFix: bitly/oauth2_proxy#359

CVE-2017-1000070 is a medium-severity (CVSS 6.1) Open Redirect vulnerability in github.com/bitly/oauth2_proxy. A fix is available for github.com/bitly/oauth2_proxy — see the affected versions and patch details below.

Open Redirect in oauth2_proxy

Also known asGHSA-jm34-xm8m-w958

Published

Jul 17, 2017

Updated

Jul 8, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.0%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs62th percentile — riskier than 62% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2017-1000070 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

1 pkg affected

🐹github.com/bitly/oauth2_proxy

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

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

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/bitly/oauth2_proxy`	all versions	2.2.0`go get github.com/bitly/oauth2_proxy@v2.2.0`

Affected Products

1 product · 1 configurations

Application

oauth2 proxyoauth2_proxy_project

≤ 2.1

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/bitly/oauth2_proxy, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/bitly/oauth2_proxy to 2.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-1000070 is resolved across your whole dependency graph.
Workarounds
Stop reflecting attacker-controlled destinations: resolve every redirect target against an allowlist of paths or hosts you own, prefer a server-side key over a full URL in the request, and reject absolute URLs entirely where the flow only ever needs a relative one.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2017-1000070 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

6.1/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

None

Raw vector

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

CWE Classification

CWE-601Open Redirect

Weaponization

No known public exploit tooling found.

OpenSSF Scorecard

Package health score

oauth2_proxy

3.5/10

Code-Review10/10

Maintained0/10

Branch-ProtectionN/A

Assessed Oct 5, 2026

Timeline

Disclosed

Jul 17, 2017

Last updated

Jul 8, 2026

Identifiers

CVE-2017-1000070

GHSA-jm34-xm8m-w958

References

Advisorynvd.nist.gov Fixgithub.com Articletools.ietf.org Webgithub.com Webgithub.com Webweb.nvd.nist.gov

Related vulnerabilities

Also affects oauth2_proxy

This CVE is medium severity; 1 of 1 other CVE affecting oauth2_proxy is rated as high or higher (top: high).

CVE-2017-1000069

Same weakness: CWE-601

This CVE is medium severity; 5 of 7 other CVEs with CWE-601 are rated as high or higher (top: critical).

CVE-2026-77609GHSA-rf68-8gjr-36q7CVE-2026-71428CVE-2026-55834CVE-2026-55461CVE-2026-54770CVE-2026-42350Browse all CWE-601

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedJul 8, 2026