GitLab EE Policy Approval Password Re-entry Bypass
CVE-2024-4784 is an improper authentication vulnerability in GitLab Enterprise Edition policy approvals. GitLab EE versions from 16.7 before 17.0.6, 17.1 before 17.1.4, and 17.2 before 17.2.2 allow bypass of the password re-entry requirement when approving a policy.
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.
An attacker able to exploit the issue can approve a policy without satisfying the intended password re-authentication control. This undermines the integrity of the policy-approval process.
If you can’t patch tonight, do this now.
If immediate patching is not possible, limit access to policy approval workflows to the smallest possible set of trusted users, review and monitor policy approval activity for anomalous or unexpected approvals, and apply additional operational controls for sensitive approvals until the upgrade is completed. GitLab.com was already running a patched version.
Patch, then assume compromise.
Upgrade GitLab EE to version 17.0.6, 17.1.4, 17.2.2, or a later supported release.
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.