CVE-2024-4283
Medium · 6.1CVSS
6.1
EPSS
0.4%
Published
Sep 16, 2024
CISA due date
—
Cloudanix analysis
A login redirect problem in GitLab could let attackers steal user accounts and access private project information.
- Exploitation
- Requires User Interaction
- Attacker needs
- None
- Complexity
- Moderate
- Impact
- Privilege Gain
- Component
- Application
- Class
- Open Redirect
- Remediation
- Upgrade
- Effort
- Medium
- Patch risk
- Low
What it actually does
Open redirect in OAuth flow under specific conditions allows an attacker to interrupt the authorization callback and hijack the resulting session or access token, enabling account takeover.
Why it matters to the business
Attackers can gain unauthorized access to repositories, issues, and other project data, potentially leading to data breaches or supply-chain compromise in organizations using GitLab EE.
How an attack unfolds
An attacker crafts a malicious redirect_uri that breaks the OAuth state validation, sends a phishing link to a victim, and intercepts the authorization code or token when the victim completes authentication, ultimately taking over the account.
How to fix it
Upgrade GitLab EE to 17.1.7, 17.2.5, or 17.3.2 (or later commits containing 84cf95d60d2691201b17bb4d41a95987ded847fb).
How to confirm the fix worked
Verify the running GitLab version is at or above the fixed releases; inspect OAuth application settings and callback URLs for unexpected external domains.
Typical attack path
- Locate an OAuth-protected endpoint in GitLab EE
- Craft a redirect_uri pointing to an attacker-controlled domain that satisfies the vulnerable conditions
- Deliver the crafted link via phishing or other social engineering
- Victim authenticates and is redirected, leaking the authorization code or token
- Attacker exchanges the leaked credential for a valid session and assumes control of the account
How to detect it
Examine web server and application logs for OAuth callback requests containing unexpected or attacker-controlled redirect_uri values; correlate with successful authentication events followed by unusual account activity.
What your security team should do
- Apply the listed version upgrades as soon as possible
- Audit all configured OAuth applications and restrict redirect URIs to known domains
- Enable and review authentication and OAuth callback logs for anomalous redirect patterns
- Consider additional monitoring for account takeover indicators such as unexpected password resets or session creations
The record
An issue has been discovered in GitLab EE affecting all versions starting from 11.1 before 17.1.7, 17.2 before 17.2.5, and 17.3 before 17.3.2. Under certain conditions an open redirect vulnerability could allow for an account takeover by breaking the OAuth flow.
Affected packages
| Ecosystem | Package | Introduced | Fixed |
|---|---|---|---|
| Bitnami | gitlab | 11.1.0 | 17.1.7 |
| Ubuntu:16.04:LTS | gitlab | 0 | No fix |
| Ubuntu:Pro:16.04:LTS | gitlab | 0 | No fix |
Related vulnerabilities
- CVE-2026-1751 A vulnerability has been discovered in GitLab CE/EE affecting all versions starting with… Also affects gitlab
- CVE-2025-3950 Exposure of Private Personal Information to an Unauthorized Actor in GitLab Also affects gitlab
- CVE-2025-9222 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in… Also affects gitlab
- CVE-2025-10569 Allocation of Resources Without Limits or Throttling in GitLab Also affects gitlab
- CVE-2025-11246 Insufficient Granularity of Access Control in GitLab Also affects gitlab
- CVE-2025-13772 Missing Authorization in GitLab Also affects gitlab
- CVE-2025-13761 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in… Also affects gitlab
- CVE-2025-13781 Missing Authorization in GitLab Also affects gitlab