CVE-2021-22218 Security feature bypass in GitLab
Attackers can spoof the author of signed commits by exploiting improper x509 certificate handling in GitLab.
- 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-22218?
CVE-2021-22218 is a low-severity vulnerability in Gitlab Gitlab, published on 8 Jun 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
All versions of GitLab CE/EE starting from 12.8 before 13.10.5, all versions starting from 13.11 before 13.11.5, and all versions starting from 13.12 before 13.12.2 were affected by an issue in the handling of x509 certificates that could be used to spoof author of signed commits.
Weakness: CWE-295
Which versions are affected by CVE-2021-22218?
1 open source package ship an affected version, including gitlab. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
gitlab Bitnami | From 12.8.0 | 13.10.5, 13.11.5, 13.12.2 |
Products include Gitlab Gitlab.
How do I fix CVE-2021-22218?
Upgrade gitlab to a fixed version for your release line: 13.10.5, 13.11.5 or 13.12.2.
Is CVE-2021-22218 being exploited?
There is no known exploitation of CVE-2021-22218 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-22218, GHSA-6qcx-wmcg-gqpq.