CVE-2024-3035 Authorization Bypass Through User-Controlled Key in GitLab
Attackers can bypass permission checks to read and write to user-owned repositories using LFS tokens in GitLab.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2024-3035?
CVE-2024-3035 is a medium-severity missing authorization vulnerability in Gitlab Gitlab, published on 8 Aug 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
A permission check vulnerability in GitLab CE/EE affecting all versions starting from 8.12 prior to 17.0.6, 17.1 prior to 17.1.4, and 17.2 prior to 17.2.2 allowed for LFS tokens to read and write to the user owned repositories.
Weakness: CWE-639
Which versions are affected by CVE-2024-3035?
1 open source package ship an affected version, including gitlab. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
gitlab Bitnami | From 8.12.0 | 17.0.6, 17.1.4, 17.2.2 |
Products include Gitlab Gitlab.
How do I fix CVE-2024-3035?
Upgrade gitlab to a fixed version for your release line: 17.0.6, 17.1.4 or 17.2.2.
Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.
Is CVE-2024-3035 being exploited?
There is no known exploitation of CVE-2024-3035 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-3035, GHSA-rvj3-54w6-vrw6, UBUNTU-CVE-2024-3035.