Loading vulnerability…
Unauthorized Access to Internal Projects in GitLab CE/EE
CVE-2024-12619 is an improper access control vulnerability in GitLab Community Edition and Enterprise Edition that affects all versions from 16.0 before 17.8.6, 17.9 before 17.9.3, and 17.10 before 17.10.1. The flaw allows an internal user to gain unauthorized access to internal projects. The available information identifies the issue as an access control failure affecting project visibility enforcement, but does not provide the specific vulnerable function or code path.
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
Successful exploitation allows an internal user to bypass intended project access restrictions and view or otherwise access internal projects that should not have been available to that user. This can result in unauthorized disclosure of project contents and related sensitive information stored within affected internal projects.
If you can’t patch tonight, do this now.
If immediate patching is not possible, reduce exposure by limiting the number of internal users, reviewing project visibility settings, and restricting use of internal visibility where feasible until the upgrade can be completed. Monitoring for unexpected access to internal projects may help detect abuse. No vendor-provided workaround is currently available in the provided information.
Patch, then assume compromise.
Upgrade GitLab CE/EE to a fixed release. Patched versions are 17.8.6, 17.9.3, and 17.10.1. Self-managed installations should update to one of these versions or a later release that includes the fix.
No public exploits tracked yet. Mallory keeps watching.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.