CVE-2021-22213 Information disclosure in GitLab
An attacker can leak OAuth access tokens by tricking a victim into visiting a malicious page using Safari.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- Available
What is CVE-2021-22213?
CVE-2021-22213 is a high-severity vulnerability in Gitlab Gitlab, published on 8 Jun 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Official description
A cross-site leak vulnerability in the OAuth flow of all versions of GitLab CE/EE since 7.10 allowed an attacker to leak an OAuth access token by getting the victim to visit a malicious page with Safari
Which versions are affected by CVE-2021-22213?
1 open source package ship an affected version, including gitlab. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
gitlab Bitnami | From 7.10.0 | 13.10.5, 13.11.5, 13.12.2 |
Products include Gitlab Gitlab.
How do I fix CVE-2021-22213?
Upgrade gitlab to a fixed version for your release line: 13.10.5, 13.11.5 or 13.12.2.
Is CVE-2021-22213 being exploited?
There is no known exploitation of CVE-2021-22213 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-22213, GHSA-q99w-5q7g-6x5x, UBUNTU-CVE-2021-22213.