CVE-2021-22236 Business logic in GitLab
Improper OAuth client ID handling allows new subscriptions to generate tokens on incorrect applications, potentially exposing data or bypassing security controls.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- Available
What is CVE-2021-22236?
CVE-2021-22236 is a medium-severity vulnerability in Gitlab Gitlab, published on 25 Aug 2021. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Official description
Due to improper handling of OAuth client IDs, new subscriptions generated OAuth tokens on an incorrect OAuth client application. This vulnerability is present in GitLab CE/EE since version 14.1.
Weakness: CWE-863
Which versions are affected by CVE-2021-22236?
1 open source package ship an affected version, including gitlab. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
gitlab Bitnami | From 14.1.0 | 14.1.2 |
Products include Gitlab Gitlab.
How do I fix CVE-2021-22236?
Upgrade gitlab to 14.1.2 or later.
Is CVE-2021-22236 being exploited?
There is no known exploitation of CVE-2021-22236 in the wild and no public exploit code.
Other vulnerabilities in Gitlab Gitlab
- CVE-2026-97229 GitLab Community Edition and Enterprise Edition Integer Overflow or Wraparound
- CVE-2026-85706 GitLab Community Edition and Enterprise Edition Path Traversal
- CVE-2023-7028 GitLab Community and Enterprise Editions Improper Access Control
- CVE-2021-22205 GitLab Community and Enterprise Editions Remote Code Execution
- CVE-2021-39935 GitLab Community and Enterprise Editions Server-Side Request Forgery (SSRF)
Sources
Also known as BIT-gitlab-2021-22236, GHSA-h963-mpc3-j9g4, UBUNTU-CVE-2021-22236.