dbcve.org
GitLabApplication

CVE-2024-4283

MEDIUM · 6.1 CVSS v3.1 Published 2024-09-16
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 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.

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 · moderate confidence

An open redirect vulnerability exists in GitLab EE's OAuth authentication flow across versions 11.1 through 17.1.7, 17.2.x before 17.2.5, and 17.3.x before 17.3.2. Under specific conditions, an attacker could manipulate the OAuth redirect flow to hijack session tokens or authorization codes, potentially leading to account takeover.

MitigationUpgrade GitLab EE to version 17.1.7, 17.2.5, 17.3.2 or later. For production environments, schedule maintenance window, backup data, test upgrade in staging, and verify OAuth functionality post-upgrade.

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:>= 11.1.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 `sudo gitlab-rake gitlab:version` or check the GitLab admin area under Help > Version. Alternatively, check the package version with `gitlab-ctl version` for self-managed installations.
    Affected if The version falls within 11.1.0 to 17.1.7, 17.2.0 to 17.2.4, or 17.3.0 to 17.3.1 (any version < 17.1.7, < 17.2.5, or < 17.3.2).
  2. Verify OAuth integration is configured
    Navigate to Admin Area > Applications (or /admin/applications) and check if any OAuth applications exist with redirect URIs configured. For GitLab.com, check User Settings > Applications.
    Affected if OAuth applications with redirect URIs are present in the GitLab instance.
  3. Inspect OAuth redirect URI configuration
    Review all OAuth applications listed in the Applications settings. Check each application's redirect URI field for whether it allows arbitrary external domains or uses wildcard patterns that could be manipulated.
    Affected if Any OAuth application has a redirect URI pointing to an external untrusted domain, or uses a wildcard/pattern that could be exploited for open redirect.

You are affected if your GitLab version is below 17.1.7, 17.2.5, or 17.3.2 AND you have OAuth applications configured with redirect URIs that could be manipulated.

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 production environments, schedule maintenance window, backup data, test upgrade in staging, and verify OAuth functionality post-upgrade.

Recommended fix High confidence

17.3.2 (or 17.2.5 / 17.1.7 depending on current version branch)

  1. 1. Backup your GitLab instance data and configuration
  2. 2. Plan maintenance window for the upgrade
  3. 3. For installations on 17.3.x: upgrade to 17.3.2 or later
  4. 4. For installations on 17.2.x: upgrade to 17.2.5 or later
  5. 5. For installations on 17.1.x or earlier: upgrade to 17.1.7 or later
  6. 6. For installations on 11.1.0 through 17.0.x: upgrade to 17.1.7 minimum, preferably 17.3.2
  7. 7. After upgrade, verify OAuth functionality is working correctly
  8. 8. Confirm the open redirect vulnerability is no longer present by testing OAuth flows
Caveat Upgrading across major versions (e.g., from 11.x to 17.x) may introduce breaking changes; review GitLab upgrade guides for migration steps and deprecated features

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

Fix this in GitLab Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-4283 — 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-4283 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