CVE-2024-4011 Improper Access Control in GitLab
Non-project members can improperly promote key results to objectives, allowing unauthorized data modification 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-4011?
CVE-2024-4011 is a low-severity missing authorization vulnerability in Gitlab Gitlab, published on 26 Jun 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
An issue was discovered in GitLab CE/EE affecting all versions starting from 16.1 prior to 16.11.5, starting from 17.0 prior to 17.0.3, and starting from 17.1 prior to 17.1.1, which allows non-project member to promote key results to objectives.
Weakness: CWE-863
Which versions are affected by CVE-2024-4011?
1 open source package ship an affected version, including gitlab. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
gitlab Bitnami | From 16.1.0 | 16.11.5, 17.0.3, 17.1.1 |
Products include Gitlab Gitlab.
How do I fix CVE-2024-4011?
Upgrade gitlab to a fixed version for your release line: 16.11.5, 17.0.3 or 17.1.1.
Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.
Is CVE-2024-4011 being exploited?
There is no known exploitation of CVE-2024-4011 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-4011, GHSA-3492-v7j6-2xgv, UBUNTU-CVE-2024-4011.