dbcve.org
GitLabApplication

CVE-2024-1211

HIGH · 8.8 CVSS v3.1 Published 2025-01-31
Fix available
A fix is available. Upgrade to 16.9.7 / 16.10.5 or later.
See remediation →
95/100
Remediation priority · Urgent
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 CE/EE affecting all versions starting from 10.6 prior to 16.9.7, starting from 16.10 prior to 16.10.5, and starting from 16.11 prior to 16.11.2 in which cross-site request forgery may have been possible on GitLab instances configured to use JWT as an OmniAuth provider.

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

A cross-site request forgery vulnerability exists in GitLab CE/EE when configured to use JWT as an OmniAuth provider. Attackers could potentially trick authenticated users into performing unintended actions on the GitLab instance by leveraging the lack of proper CSRF protection on JWT authentication flows.

MitigationUpdate GitLab to version 16.9.7, 16.10.5, or 16.11.2 or later to patch this vulnerability. If immediate patching is not feasible, consider disabling the JWT OmniAuth provider or implementing additional CSRF token validation at the application layer.

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:>= 10.6.0, < 16.9.7>= 16.10.0, < 16.10.5>= 16.11.0, < 16.11.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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Check installed GitLab version
    Run `sudo gitlab-rake gitlab:env:info` or access the GitLab admin area and navigate to /help/version to retrieve the exact version number
    Affected if The installed version falls within any of these ranges: 10.6.0 to 16.9.6, 16.10.0 to 16.10.4, or 16.11.0 to 16.11.1
  2. Verify JWT OmniAuth provider is enabled
    Examine the GitLab configuration file (typically /etc/gitlab/gitlab.rb or /etc/gitlab/gitlab.yml) for the `gitlab_omniauth_providers` setting and look for a provider block with 'jwt' as the name
    Affected if JWT is listed as an enabled OmniAuth provider in the configuration
  3. Check admin panel OAuth providers
    Log into the GitLab admin area, navigate to Settings > Authentication > OAuth providers, and review the list of enabled OAuth providers
    Affected if JWT appears as an enabled provider in the admin panel

You are affected only if your GitLab version is within the vulnerable ranges AND JWT is configured as an OmniAuth provider.

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 16.9.7 / 16.10.5 / 16.11.2 or later
Fixed in 16.9.716.10.516.11.2
Interim mitigation

Update GitLab to version 16.9.7, 16.10.5, or 16.11.2 or later to patch this vulnerability. If immediate patching is not feasible, consider disabling the JWT OmniAuth provider or implementing additional CSRF token validation at the application layer.

Recommended fix High confidence

16.9.7, 16.10.5, or 16.11.2 (depending on your current major.minor version)

  1. 1. Back up your GitLab instance database and configuration files
  2. 2. Plan your upgrade path based on your current version - if on 16.9.x upgrade to 16.9.7, if on 16.10.x upgrade to 16.10.5, if on 16.11.x upgrade to 16.11.2
  3. 3. Review GitLab upgrade documentation for your specific version path (https://docs.gitlab.com/ee/update/)
  4. 4. Stop GitLab services before upgrading
  5. 5. Update GitLab to the appropriate fixed version using your package manager or source
  6. 6. Run GitLab database migrations: sudo gitlab-rake db:migrate
  7. 7. Restart GitLab services
  8. 8. Verify the instance is operational and test OmniAuth JWT functionality
Caveat Standard GitLab upgrade considerations apply - review release notes for breaking changes between your current version and target version, especially for major version jumps

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

Fix this in GitLab Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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