CVE-2020-4037

Description

In OAuth2 Proxy from version 5.1.1 and less than version 6.0.0, users can provide a redirect address for the proxy to send the authenticated user to at the end of the authentication flow. This is expected to be the original URL that the user was trying to access. This redirect URL is checked within the proxy and validated before redirecting the user to prevent malicious actors providing redirects to potentially harmful sites. This has been fixed in version 6.0.0.

Severity
MEDIUM
CVSS v3
4.3
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N · source cna
Exploit chance (EPSS)
0.896%
chance of exploitation in the next 30 days
higher than 60.1% of scored CVEs · 2026-11-17
CISA KEV
Not listed
Public exploit code
None public
Exploit references (NVD and CNA): 0
Metasploit modules: 0
Nuclei templates: 0

Weakness

Timeline

  1. 2020-06-29Published by the CNA19:45 UTC
  2. 2021-12-20GitHub advisory published (GHSA-5m6c-jp6f-2vcv)539 days after publication

The timeline shows what already happened. To be told when this CVE changes next, watch it from the API.

Exploit and advisory records

GitHub advisory GHSA-5m6c-jp6f-2vcv, affected packages:

PackageVulnerable versionsFixed in
Go github.com/oauth2-proxy/oauth2-proxyfrom 5.1.1 before 6.0.06.0.0

Affected products

Products listed as vulnerable. Upgrade to the version under "Fixed in", or a later one.

ProductVulnerable versionsFixed in
oauth2_proxy_project oauth2_proxyfrom 5.1.1 before 6.0.0fixed in 6.0.06.0.0

Products and versions as NVD and the vendor that published the CVE list them.

References

Get more CVE data from the API.

Free without a key or signup. Pro adds monitoring and higher limits: pricing.

Sources