dbcve.org
GitLabApplication

CVE-2024-2829

HIGH · 7.5 CVSS v3.1 Published 2024-04-25
Fix available
A fix is available. Upgrade to 16.9.6 / 16.10.4 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 12.5 before 16.9.6, all versions starting from 16.10 before 16.10.4, all versions starting from 16.11 before 16.11.1. A crafted wildcard filter in FileFinder may lead to a denial of service.

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 denial of service vulnerability exists in GitLab CE/EE's FileFinder component where a crafted wildcard filter can cause excessive resource consumption, potentially making the service unavailable. The vulnerability is triggered by specially crafted input to the FileFinder feature.

MitigationUpgrade GitLab to version 16.9.6, 16.10.4, 16.11.1 or later. Alternatively, if immediate upgrade is not feasible, consider restricting or disabling the FileFinder feature until the patch can be applied.

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.5.0, < 16.9.6>= 16.10.0, < 16.10.4= 16.11.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
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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. Identify GitLab version
    Run `gitlab-rake gitlab:env:info` or check the GitLab UI under Help > Version. On Omnibus installs, also check `/opt/gitlab/version`.
    Affected if The version falls within >= 12.5.0 AND < 16.9.6, OR >= 16.10.0 AND < 16.10.4, OR equals 16.11.0
  2. Confirm FileFinder feature is accessible
    Log into GitLab and navigate to any project repository. Look for a file search or finder functionality, typically accessed via the repository file browser or pressing 't' keyboard shortcut.
    Affected if The FileFinder feature is available and accessible to users in the GitLab instance
  3. Determine if instance has active projects with repositories
    Check if any projects exist in the GitLab instance by viewing the projects dashboard or running `gitlab-rake gitlab:metrics:projects` to count active repositories.
    Affected if There are active projects with repositories, making the FileFinder feature usable and the attack surface present

If the GitLab version is within the affected ranges AND the FileFinder feature is accessible to users, the environment is vulnerable to the DoS condition described in CVE-2024-2829.

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.6 / 16.10.4 or later
Fixed in 16.9.616.10.4
Interim mitigation

Upgrade GitLab to version 16.9.6, 16.10.4, 16.11.1 or later. Alternatively, if immediate upgrade is not feasible, consider restricting or disabling the FileFinder feature until the patch can be applied.

Recommended fix High confidence

Upgrade to GitLab 16.9.6, 16.10.4, or 16.11.1 (or later)

  1. 1. Backup your GitLab instance and database before upgrading.
  2. 2. For GitLab Omnibus installations: Run 'sudo apt-get update && sudo apt-get install gitlab-ce' (or 'gitlab-ee' for Enterprise Edition).
  3. 3. For source installations: Stop GitLab, download the appropriate version from gitlab.com, extract, and run the migration scripts.
  4. 4. After upgrade, run 'sudo gitlab-ctl reconfigure' for Omnibus installations.
  5. 5. Verify the upgrade was successful by checking the GitLab version at /admin/about.
  6. 6. Test the FileFinder functionality to confirm the vulnerability is resolved.
Caveat Major version upgrades in GitLab may include breaking changes; review the Changelog for your target version before upgrading

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

Fix this in GitLab Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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