dbcve.org
GitLabApplication

CVE-2024-4612

MEDIUM · 6.1 CVSS v3.1 Published 2024-09-12
Fix available
A fix is available. Upgrade to 17.1.7 / 17.2.5 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
An issue has been discovered in GitLab EE affecting all versions starting from 12.9 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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

An open redirect vulnerability exists in GitLab EE's OAuth authentication flow across versions 12.9 through 17.3.1 (before patched releases). The vulnerability allows attackers to manipulate the OAuth redirect URI, potentially breaking the flow and enabling account takeover by hijacking session tokens or authorization codes.

MitigationUpgrade GitLab EE to version 17.1.7, 17.2.5, 17.3.2 or later. For systems unable to upgrade immediately, restrict OAuth provider configurations and monitor for suspicious redirect patterns in authentication requests.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
GitLabApplication
Affected:>= 12.9.0, < 17.1.7>= 17.2.0, < 17.2.5>= 17.3.0, < 17.3.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed GitLab version
    Run 'gitlab-rake gitlab:version' or access the Admin Area > Settings > Metrics and profiling > Version in the GitLab web interface
    Affected if The reported version falls within any of these ranges: >= 12.9.0 and < 17.1.7, OR >= 17.2.0 and < 17.2.5, OR >= 17.3.0 and < 17.3.2
  2. Confirm OAuth integration is in use
    Navigate to Admin Area > Settings > OAuth in the GitLab web interface, or run 'gitlab-rake gitlab:oauth:list' if available, to list configured OAuth providers
    Affected if Any OAuth provider (e.g., GitHub, Google, Okta, custom SAML/OIDC) is configured and enabled for user authentication
  3. Review OAuth redirect URI configurations
    Inspect the redirect_uri or redirect_url parameter for each OAuth provider in Admin Area > Settings > OAuth; verify no URIs contain untrusted external domains or unusual parameters
    Affected if Any configured OAuth redirect URI points to an external domain outside your organization's expected identity provider, or contains unexpected query parameters that could indicate manipulation attempts

You are affected if your GitLab version is in the vulnerable range AND OAuth authentication is enabled with a potentially manipulable redirect URI.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 17.1.7 / 17.2.5 / 17.3.2 or later
Fixed in 17.1.717.2.517.3.2
Interim mitigation

Upgrade GitLab EE to version 17.1.7, 17.2.5, 17.3.2 or later. For systems unable to upgrade immediately, restrict OAuth provider configurations and monitor for suspicious redirect patterns in authentication requests.

Recommended fix High confidence

Upgrade to GitLab 17.3.2 or later (recommended: latest 17.3.x stable release)

  1. 1. Back up your GitLab database and repository data before proceeding with the upgrade
  2. 2. Review the GitLab upgrade prerequisites for your installation method ( Omnibus or source)
  3. 3. For Omnibus installations: Run 'gitlab-ctl stop' to stop GitLab services
  4. 4. Update your package repository to fetch the latest available packages
  5. 5. For Omnibus: Run 'apt-get update' or 'yum update' depending on your OS
  6. 6. Install the updated GitLab package. For Omnibus: 'apt-get install gitlab-ee' or 'yum install gitlab-ee'
  7. 7. Run 'gitlab-ctl reconfigure' to apply the configuration
  8. 8. Run 'gitlab-ctl start' to start GitLab services
Caveat Review GitLab 17.3 release notes for any known breaking changes or required manual migration steps before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in GitLab Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-4612 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-4612 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data