CVE-2021-21291: Subdomain checking of whitelisted domains could allow unintended redirects in oauth2-proxy

CVE-2021-21291 · Severity: low · CVSS 3.1 · Published 2024-08-21

Subdomain checking of whitelisted domains could allow unintended redirects in oauth2-proxy in github.com/oauth2-proxy/oauth2-proxy

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

Quick answers

Is CVE-2021-21291 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2021-21291 being exploited in the wild.
How severe is CVE-2021-21291?
Low severity, with a CVSS score of 3.1, published 21 August 2024.
Which products and versions are affected?
github.com/oauth2-proxy/oauth2-proxy (Go) SEMVER:introduced=0, SEMVER:introduced=0,last_affected=3.2.0; github.com/oauth2-proxy/oauth2-proxy/v7 (Go) SEMVER:introduced=0,fixed=7.0.0.
Is there a fix for CVE-2021-21291?
Yes. github.com/oauth2-proxy/oauth2-proxy/v7 (Go): upgrade to 7.0.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2021-21291?
Check whether you run github.com/oauth2-proxy/oauth2-proxy (Go) or github.com/oauth2-proxy/oauth2-proxy/v7 (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/v7 (Go): upgrade to 7.0.0 or later
    go get github.com/oauth2-proxy/oauth2-proxy/v7@v7.0.0

Affected products

  • github.com/oauth2-proxy/oauth2-proxy (Go) SEMVER:introduced=0, SEMVER:introduced=0,last_affected=3.2.0
  • github.com/oauth2-proxy/oauth2-proxy/v7 (Go) SEMVER:introduced=0,fixed=7.0.0

Identifiers

  • CVE-2021-21291
  • GHSA-4mf2-f3wh-gvf2
  • GO-2022-0790

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