Access Control Flaw in GitLab EE Affects Multiple Versions
CVE-2024-12244

4.3MEDIUM

Key Information:

Vendor
Gitlab
Status
Vendor
CVE Published:
24 April 2025

Badges

📈 Score: 281👾 Exploit Exists🟡 Public PoC

What is CVE-2024-12244?

CVE-2024-12244 is an access control vulnerability found in GitLab EE, a popular open-source platform used for source code management and DevOps lifecycle. This vulnerability allows unauthorized users to gain visibility into restricted project information, even when specific project features are disabled. The issue affects multiple versions of GitLab EE, raising concerns for organizations that rely on this platform to secure their source code and manage collaborative projects. If exploited, it could lead to an unintended disclosure of sensitive project details, risking intellectual property and confidential data.

Technical Details

The vulnerability arises from improper access control mechanisms within GitLab EE, impacting all versions from 17.7 prior to 17.9.7, 17.10 prior to 17.10.5, and 17.11 prior to 17.11.1. Attackers can exploit this flaw by bypassing intended restrictions, allowing them to view sensitive information related to certain projects. This misconfiguration highlights a failure to properly enforce user permissions, which is critical for maintaining the confidentiality of project data.

Potential Impact of CVE-2024-12244

  1. Data Exposure: The most significant impact of this vulnerability is the potential exposure of sensitive project information. Unauthorized users could access confidential data that should remain restricted, potentially leading to data leaks.

  2. Intellectual Property Risks: Organizations risk losing valuable intellectual property if restricted information is disclosed. Competitors or malicious actors could use this access to gain insights into proprietary technologies, project strategies, or future plans.

  3. Reputation Damage: The exploitation of this vulnerability could harm an organization's reputation. Breaches of trust and the associated fallout from exposing sensitive information can lead to diminished client confidence and a weakened market position.

Affected Version(s)

GitLab 17.7 < 17.9.7

GitLab 17.10 < 17.10.5

GitLab 17.11 < 17.11.1

Exploit Proof of Concept (PoC)

PoC code is written by security researchers to demonstrate the vulnerability can be exploited. PoC code is also a key component for weaponization which could lead to ransomware.

References

CVSS V3.1

Score:
4.3
Severity:
MEDIUM
Confidentiality:
Low
Integrity:
None
Availability:
Low
Attack Vector:
Network
Attack Complexity:
Low
Privileges Required:
Low
User Interaction:
None
Scope:
Unchanged

Timeline

  • 🟡

    Public PoC available

  • 👾

    Exploit known to exist

  • Vulnerability published

  • Vulnerability Reserved

Credit

Thanks [mateuszek](https://hackerone.com/mateuszek) for reporting this vulnerability through our HackerOne bug bounty program
.