CVE & CISA-KEV Catalog

CVE-2021-21411

MEDIUM
5.5
CVSS v3
NVD

Description

OAuth2-Proxy is an open source reverse proxy that provides authentication with Google, Github or other providers. The `--gitlab-group` flag for group-based authorization in the GitLab provider stopped working in the v7.0.0 release. Regardless of the flag settings, authorization wasn't restricted. Additionally, any authenticated users had whichever groups were set in `--gitlab-group` added to the new `X-Forwarded-Groups` header to the upstream application. While adding GitLab project based authorization support in #630, a bug was introduced where the user session's groups field was populated with the `--gitlab-group` config entries instead of pulling the individual user's group membership from the GitLab Userinfo endpoint. When the session groups where compared against the allowed groups for authorization, they matched improperly (since both lists were populated with the same data) so authorization was allowed. This impacts GitLab Provider users who relies on group membership for authorization restrictions. Any authenticated users in your GitLab environment can access your applications regardless of `--gitlab-group` membership restrictions. This is patched in v7.1.0. There is no workaround for the Group membership bug. But `--gitlab-project` can be set to use Project membership as the authorization checks instead of groups; it is not broken.

How to fix

Remediation Available
oauth2 proxyNVD
Affected:>= 7.0.0, < 7.1.0Fixed in:7.1.0CVE-2021-21411derived from NVD

Remediation is compiled from vendor and distribution security advisories. Always confirm against the linked source for your exact version and platform.

CVSS v3 Vector

Exploitability

Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredHigh
User InteractionNone
ScopeChanged

Impact

ConfidentialityLow
IntegrityLow
AvailabilityNone

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:N

Exploit Intelligence

0.99%probability of exploitation in 30 days
58thpercentile

Moderate risk: more likely to be exploited than 58% of all known CVEs.

References

Related Vulnerabilities

Other CWE-863 (Incorrect Authorization) vulnerabilities, ordered by exploit likelihood. View all

CVESeverityCVSSEPSSExploitedFix
CVE-2023-22518Critical9.8100%KEV + RansomFix
CVE-2023-38035Critical9.8100%KEV + Ransom-
CVE-2022-46169Critical9.8100%KEVFix
CVE-2025-29927Critical9.1100%-Fix
CVE-2024-38856Critical9.899%KEVFix
CVE-2020-36289Medium5.399%-Fix
Embed a live status badge for CVE-2021-21411
CVE-2021-21411 severity badge

Markdown

[![CVE-2021-21411](https://tridentstack.com/cve/badge/CVE-2021-21411.svg)](https://tridentstack.com/cve/CVE-2021-21411)

HTML

<a href="https://tridentstack.com/cve/CVE-2021-21411"><img src="https://tridentstack.com/cve/badge/CVE-2021-21411.svg" alt="CVE-2021-21411"></a>

Find and fix vulnerabilities across your fleet

TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.

Start free

This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2024-11-21.