CVE-2023-2030 Improper Verification of Cryptographic Signature in GitLab
Attackers can modify metadata of signed commits in GitLab, bypassing cryptographic signature verification and compromising code integrity.
- 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-2023-2030?
CVE-2023-2030 is a low-severity vulnerability in Gitlab Gitlab, published on 12 Jan 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Official description
An issue has been discovered in GitLab CE/EE affecting all versions from 12.2 prior to 16.5.6, 16.6 prior to 16.6.4, and 16.7 prior to 16.7.2 in which an attacker could potentially modify the metadata of signed commits.
Weakness: CWE-347
Which versions are affected by CVE-2023-2030?
1 open source package ship an affected version, including gitlab. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
gitlab Bitnami | From 12.2.0 | 16.5.6, 16.6.4, 16.7.2 |
Products include Gitlab Gitlab.
How do I fix CVE-2023-2030?
Upgrade gitlab to a fixed version for your release line: 16.5.6, 16.6.4 or 16.7.2.
Is CVE-2023-2030 being exploited?
There is no known exploitation of CVE-2023-2030 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-2023-2030, GHSA-797c-p7mm-pf4h, UBUNTU-CVE-2023-2030.