CVE-2020-11053: Open Redirect in OAuth2 Proxy

CVE-2020-11053 · Severity: low · CVSS 3.1 · Published 2021-12-20

Open Redirect in OAuth2 Proxy

Technologies: github.com/oauth2-proxy/oauth2-proxy (Go). Vendors: Go.

Quick answers

Is CVE-2020-11053 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2020-11053 being exploited in the wild.
How severe is CVE-2020-11053?
Low severity, with a CVSS score of 3.1, published 20 December 2021.
Which products and versions are affected?
github.com/oauth2-proxy/oauth2-proxy (Go) SEMVER:introduced=0,fixed=5.1.1.
Is there a fix for CVE-2020-11053?
Yes. github.com/oauth2-proxy/oauth2-proxy (Go): upgrade to 5.1.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2020-11053?
Check whether you run github.com/oauth2-proxy/oauth2-proxy (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • github.com/oauth2-proxy/oauth2-proxy (Go): upgrade to 5.1.1 or later
    go get github.com/oauth2-proxy/oauth2-proxy@v5.1.1

Affected products

  • github.com/oauth2-proxy/oauth2-proxy (Go) SEMVER:introduced=0,fixed=5.1.1

Identifiers

  • CVE-2020-11053
  • GHSA-j7px-6hwj-hpjg

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.