CVE-2024-6389: Exposure of Sensitive System Information to an Unauthorized Control Sphere in GitLab
An issue was discovered in GitLab CE/EE affecting all versions starting with 17.0 before 17.1.7, 17.2 before 17.2.5, and 17.3 before 17.3.2. An attacker as a guest user was able to access commit information via the release Atom endpoint, contrary to permissions. This is a medium severity issue (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N, 4.3). It is now mitigated in the latest release and is assigned CVE-2024-6389.
Other sources
An issue was discovered in GitLab-CE/EE affecting all versions starting with 17.0 before 17.1.7, 17.2 before 17.2.5, and 17.3 before 17.3.2. An attacker as a guest user was able to access commit information via the release Atom endpoint, contrary to permissions.
— MITRE
Affected Software
Remediation
Information
Event History
Peer vulnerabilities
Found alongside the following vulnerabilities.
Frequently Asked Questions
What is the severity of CVE-2024-6389?
CVE-2024-6389 has a moderate severity level that affects GitLab versions that do not properly restrict guest user permissions.
How do I fix CVE-2024-6389?
To fix CVE-2024-6389, upgrade GitLab to versions 17.1.7, 17.2.5, or 17.3.2 or later.
Who is affected by CVE-2024-6389?
CVE-2024-6389 affects all GitLab-CE and GitLab-EE versions starting from 17.0 up to but not including the specified patched versions.
What type of vulnerability is CVE-2024-6389?
CVE-2024-6389 is a permissions vulnerability that allows unauthorized access to commit information by guest users.
What impact does CVE-2024-6389 have on GitLab users?
The impact of CVE-2024-6389 is that guest users can access sensitive commit information, potentially exposing project details.