Authentication Bypass by Primary Weakness in GitLab (CVE-2024-4784)
GitLab EE versions 16.7 up to but not including 17.0.6, 17.1 up to but not including 17.1.4, and 17.2 up to but not including 17.2.2 contain a vulnerability that allows bypassing the password re-entry requirement for policy approval. This authentication bypass could undermine security controls that rely on password confirmation for sensitive actions.
AI Analysis
Technical Summary
CVE-2024-4784 is a vulnerability in GitLab EE affecting versions >=16.7.0 <17.0.6, >=17.1.0 <17.1.4, and >=17.2.0 <17.2.2. The flaw allows an attacker to bypass the password re-entry requirement when approving a policy, potentially enabling unauthorized approval actions without proper authentication. This weakness compromises the intended secondary authentication step designed to protect sensitive operations.
Potential Impact
The vulnerability impacts the authentication mechanism by allowing bypass of the password re-entry step required for policy approval. This could lead to unauthorized policy approvals, weakening security controls within GitLab EE. There are no known exploits in the wild at this time.
Mitigation Recommendations
A patch is available for this vulnerability. Users should upgrade GitLab EE to versions 17.0.6 or later, 17.1.4 or later, or 17.2.2 or later to remediate this issue.
Authentication Bypass by Primary Weakness in GitLab (CVE-2024-4784)
Description
GitLab EE versions 16.7 up to but not including 17.0.6, 17.1 up to but not including 17.1.4, and 17.2 up to but not including 17.2.2 contain a vulnerability that allows bypassing the password re-entry requirement for policy approval. This authentication bypass could undermine security controls that rely on password confirmation for sensitive actions.
Affected software
pkg:bitnami/gitlabRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2024-4784 is a vulnerability in GitLab EE affecting versions >=16.7.0 <17.0.6, >=17.1.0 <17.1.4, and >=17.2.0 <17.2.2. The flaw allows an attacker to bypass the password re-entry requirement when approving a policy, potentially enabling unauthorized approval actions without proper authentication. This weakness compromises the intended secondary authentication step designed to protect sensitive operations.
Potential Impact
The vulnerability impacts the authentication mechanism by allowing bypass of the password re-entry step required for policy approval. This could lead to unauthorized policy approvals, weakening security controls within GitLab EE. There are no known exploits in the wild at this time.
Mitigation Recommendations
A patch is available for this vulnerability. Users should upgrade GitLab EE to versions 17.0.6 or later, 17.1.4 or later, or 17.2.2 or later to remediate this issue.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- BIT-gitlab-2024-4784
- Osv Schema Version
- 1.5.0
- Aliases
- ["CVE-2024-4784"]
- Ecosystems
- ["Bitnami"]
- Database Specific Severity
- Medium
Threat ID: 6aa329a391cc7f3848d1c539
Added to database: 09/10/2026, 22:05:23 UTC
Last enriched: 09/10/2026, 22:33:54 UTC
Last updated: 09/11/2026, 03:02:34 UTC
Views: 5
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.