GitLab Permission Check Vulnerability Affects User Repositories
CVE-2024-3035

8.1HIGH

Key Information:

Vendor
Gitlab
Status
Gitlab
Vendor
CVE Published:
8 August 2024

Badges

👾 Exploit Exists🟡 Public PoC

Summary

A vulnerability in GitLab CE and EE products allows a permission check issue that affects all versions from 8.12 up to, but not including, 17.0.6, as well as 17.1 prior to 17.1.4 and 17.2 prior to 17.2.2. This flaw permits LFS tokens to gain unauthorized read and write access to user-owned repositories, possibly compromising sensitive data and project integrity while allowing malicious actors to manipulate repository contents without proper authorization. The issue has been tracked for resolution and requires immediate attention for users relying on these GitLab versions.

Affected Version(s)

GitLab 8.12 < 17.0.6

GitLab 17.1 < 17.1.4

GitLab 17.2 < 17.2.2

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.

CVE-2024-3035 - Proof of Concept

References

https://gitlab.com/gitlab-org/gitlab/-/issues/452297
issue-trackingpermissions-required
https://hackerone.com/reports/2424715
technical-descriptionexploitpermissions-required

CVSS V3.1

Score:
8.1
Severity:
HIGH
Confidentiality:
High
Integrity:
High
Availability:
High
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 [pwnie](https://hackerone.com/pwnie) for reporting this vulnerability through our HackerOne bug bounty program
.