dbcve.org
GitLabApplication

CVE-2024-11129

HIGH · 7.5 CVSS v3.1 Published 2025-04-10
Fix available
A fix is available. Upgrade to 17.8.6 / 17.8.7 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 EE affecting all versions from 17.1 before 17.8.7, 17.9 before 17.9.6, and 17.10 before 17.10.4. This allows attackers to perform targeted searches with sensitive keywords to get the count of issues containing the searched term."

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 information disclosure vulnerability in GitLab EE's search functionality. Attackers can perform targeted keyword searches on issues and obtain the count of matching issues, revealing whether sensitive topics (passwords, API keys, vulnerabilities) exist in the issue tracker without needing access to the actual issue content.

MitigationUpgrade GitLab EE to version 17.8.7, 17.9.6, or 17.10.4 or later depending on your current branch.

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:>= 17.1.0, < 17.8.6>= 17.1.0, < 17.8.7>= 17.9.0, < 17.9.6>= 17.10.0, < 17.10.4

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
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 GitLab EE version
    Log into the GitLab admin panel and navigate to the Admin Area > Overview > Dashboard, or run `sudo gitlab-rake gitlab:env:info` to see the installed version
    Affected if The installed version falls within 17.1.0 to 17.8.5, 17.9.0 to 17.9.5, or 17.10.0 to 17.10.3
  2. Identify search exposure
    Check whether the GitLab instance allows search queries from unauthenticated users or users without project access. Try accessing the search API endpoint `/api/v4/search?scope=issues&search=password` without authentication or with a low-privilege user token
    Affected if The search endpoint returns issue counts to users who should not have visibility into those issues
  3. Verify issue visibility controls
    Review project and group settings under Settings > Visibility and access controls. Confirm whether issues are set to public or if the search indexer exposes issue metadata to unauthorized users
    Affected if Issues or search results are accessible to users lacking read permissions on the issue tracker

You are affected if your GitLab EE version is between 17.1.0 and 17.8.5, 17.9.0 and 17.9.5, or 17.10.0 and 17.10.3 AND your search functionality returns issue counts to users without proper issue visibility permissions

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.8.6 / 17.8.7 / 17.9.6 or later
Fixed in 17.8.617.8.717.9.6
Interim mitigation

Upgrade GitLab EE to version 17.8.7, 17.9.6, or 17.10.4 or later depending on your current branch.

Recommended fix High confidence

17.8.7 (for 17.1-17.8.x branches), 17.9.6 (for 17.9.x branch), or 17.10.4 (for 17.10.x branch)

  1. 1. Identify the currently installed GitLab version using `sudo gitlab-rake gitlab:env:info` or checking the GitLab admin panel.
  2. 2. Determine which version branch the current installation falls into (17.1-17.8.x, 17.9.x, or 17.10.x).
  3. 3. For installations on 17.1.x through 17.8.x: upgrade to version 17.8.7 or later.
  4. 4. For installations on 17.9.x: upgrade to version 17.9.6 or later.
  5. 5. For installations on 17.10.x: upgrade to version 17.10.4 or later.
  6. 6. Follow standard GitLab upgrade procedures using GitLab's official upgrade guides (https://docs.gitlab.com/ee/update/).
  7. 7. After upgrade, verify the fix by testing the issue search functionality to confirm sensitive keyword counts are no longer exposed.
Caveat Standard GitLab minor version upgrades typically have minimal breaking changes; review release notes for any deprecations

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

Fix this in GitLab Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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