Skip to main content

Over 150 LLM Providers · Over 5,300 Models The most extensible AI-powered pentesting platform. Open source. Star on GitHub

CVE-2020-11053

7.1 · HIGH
Published May 7, 2020 oauth2_proxy_project CWE-601 EPSS 0.79% (54th pctl)

Overview

CVE-2020-11053 is a high-severity vulnerability affecting oauth2_proxy_project oauth2_proxy. It was published on May 7, 2020 and has a CVSS 3.1 base score of 7.1 (HIGH).

This vulnerability has a CVSS 3.1 base score of 7.1, rated HIGH. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

Technical Description

In OAuth2 Proxy before 5.1.1, there is an open redirect vulnerability. 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. However, by crafting a redirect URL with HTML encoded whitespace characters the validation could be bypassed and allow a redirect to any URL provided. This has been patched in 5.1.1.

Remediation

Check the references section for vendor advisories and patches from oauth2_proxy_project. Update oauth2_proxy to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Affected Products

Vendor Product Versions Status
oauth2_proxy_project oauth2_proxy >= 0, < 5.1.1 Affected

Frequently Asked Questions

What is CVE-2020-11053?

CVE-2020-11053 is a high-severity vulnerability affecting oauth2_proxy_project oauth2_proxy. It was published on May 7, 2020 and has a CVSS 3.1 base score of 7.1 (HIGH).

How severe is CVE-2020-11053?

This vulnerability has a CVSS 3.1 base score of 7.1, rated HIGH. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-2020-11053?

Check the references section for vendor advisories and patches from oauth2_proxy_project. Update oauth2_proxy to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2020-11053?

CyberStrike's AI-powered security agents can automatically detect CVE-2020-11053 across your infrastructure using autonomous pentesting, DAST scanning, and HackBrowser. The platform continuously monitors for known vulnerabilities and provides actionable remediation guidance prioritized by real-world exploitability.