dbcve.org
GitLabApplication

CVE-2024-0410

HIGH · 7.7 CVSS v3.1 Published 2024-02-22
Fix available
A fix is available. Upgrade to 16.7.6 / 16.8.3 or later.
See remediation →
81/100
Remediation priority · High
Remotely reachable

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 authorization bypass vulnerability was discovered in GitLab affecting versions 15.1 prior to 16.7.6, 16.8 prior to 16.8.3, and 16.9 prior to 16.9.1. A developer could bypass CODEOWNERS approvals by creating a merge conflict.

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

This is an authorization bypass vulnerability in GitLab where a developer can circumvent CODEOWNERS approval requirements by creating a merge conflict. CODEOWNERS is a feature that enforces mandatory review/approval from designated owners for certain file paths, but the vulnerability allows attackers to bypass this security control.

MitigationUpgrade GitLab to versions 16.7.6, 16.8.3, 16.9.1 or later. This is a standard patch upgrade following GitLab's documented upgrade path.

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:>= 15.1.0, < 16.7.6>= 16.8.0, < 16.8.3= 16.9.0

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
High
Privileges
Low
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/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. Identify installed GitLab version
    Access the GitLab admin area (usually at /admin) or check the version via the GitLab UI footer, or run `gitlab-rake gitlab:env:info` on the server
    Affected if Version falls within 15.1.0 to 16.7.5, 16.8.0 to 16.8.2, or equals 16.9.0
  2. Verify CODEOWNERS file exists in repository
    Check repositories for a `.gitlab/CODEOWNERS` file at the root or in subdirectories
    Affected if A CODEOWNERS file exists and defines approval requirements for certain paths
  3. Confirm CODEOWNERS approval rules are enforced
    Review merge request settings in the project to ensure 'Code owner approval required' or similar CODEOWNERS enforcement is enabled under protected branches or merge request settings
    Affected if CODEOWNERS approval is configured as mandatory for merge requests
  4. Check for merge requests with unresolved conflicts
    Review recent merge requests to see if any were merged despite CODEOWNERS approval requirements being defined but possibly bypassed through conflict status manipulation
    Affected if Merge requests were completed without required CODEOWNERS approvals when merge conflicts existed

The environment is affected if the installed GitLab version is 15.1.0 through 16.7.5, 16.8.0 through 16.8.2, or exactly 16.9.0, and CODEOWNERS approval rules are in use for the repository.

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.7.6 / 16.8.3 or later
Fixed in 16.7.616.8.3
Interim mitigation

Upgrade GitLab to versions 16.7.6, 16.8.3, 16.9.1 or later. This is a standard patch upgrade following GitLab's documented upgrade path.

Recommended fix High confidence

16.7.6, 16.8.3, or 16.9.1 (or latest stable release)

  1. Plan a maintenance window and backup your GitLab instance and database
  2. Identify your current GitLab version
  3. If running 16.7.x: upgrade to 16.7.6 or later
  4. If running 16.8.x: upgrade to 16.8.3 or later
  5. If running 16.9.0: upgrade to 16.9.1 or later
  6. Alternatively, upgrade to the latest stable GitLab release (recommended for comprehensive security fixes)
  7. After upgrade, verify the installation was successful
  8. Test that CODEOWNERS approval requirements are properly enforced for merge requests
Caveat Review GitLab release notes for breaking changes between your current version and target version; major version upgrades may require additional migration steps

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
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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