CVE-2024-6502 Incorrect Provision of Specified Functionality in GitLab
An attacker can create a branch with the same name as a deleted tag, potentially causing confusion or unauthorized access to repository content.
- 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-2024-6502?
CVE-2024-6502 is a medium-severity vulnerability in Gitlab Gitlab, published on 22 Aug 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 was discovered in GitLab CE/EE affecting all versions starting from 8.2 prior to 17.1.6 starting from 17.2 prior to 17.2.4, and starting from 17.3 prior to 17.3.1, which allows an attacker to create a branch with the same name as a deleted tag.
Weakness: CWE-684
Which versions are affected by CVE-2024-6502?
1 open source package ship an affected version, including gitlab. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
gitlab Bitnami | From 8.2.0 | 17.1.6, 17.2.4, 17.3.1 |
Products include Gitlab Gitlab.
How do I fix CVE-2024-6502?
Upgrade gitlab to a fixed version for your release line: 17.1.6, 17.2.4 or 17.3.1.
Is CVE-2024-6502 being exploited?
There is no known exploitation of CVE-2024-6502 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-2024-6502, GHSA-j5xm-2wp4-36g2, UBUNTU-CVE-2024-6502.