dbcve.org
GitLabApplication

CVE-2024-2191

MEDIUM · 5.3 CVSS v3.1 Published 2024-06-27
Fix available
A fix is available. Upgrade to 16.11.5 / 17.0.3 or later.
See remediation →
62/100
Remediation priority · Elevated
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 was discovered in GitLab CE/EE affecting all versions starting from 16.9 prior to 16.11.5, starting from 17.0 prior to 17.0.3, and starting from 17.1 prior to 17.1.1, which allows merge request title to be visible publicly despite being set as project members only.

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 broken access control vulnerability in GitLab CE/EE allows merge request titles that were configured to be visible only to project members to be exposed publicly. This information disclosure affects versions 16.9 through 16.11.4, 17.0 through 17.0.2, and 17.1 through 17.1.0.

MitigationUpgrade GitLab to version 16.11.5, 17.0.3, 17.1.1 or later to remediate the access control bypass on merge request title visibility.

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:>= 16.9.0, < 16.11.5>= 17.0.0, < 17.0.3= 17.1.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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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. Check GitLab version
    Run 'sudo gitlab-rake gitlab:version' or access the GitLab admin panel to view the installed version
    Affected if Version is 16.9.0 through 16.11.4, 17.0.0 through 17.0.2, or 17.1.0 exactly
  2. Identify merge requests with member-only visibility
    Navigate to the project merge requests list and check each merge request's visibility setting in the merge request details or project settings
    Affected if There are merge requests configured with visibility restricted to project members only
  3. Verify public access to restricted merge request titles
    Open a browser in incognito mode (unauthenticated) and attempt to view the merge requests identified as member-only; check if the title is visible on the merge request page or in public project activity
    Affected if Merge request titles configured as visible only to project members are accessible without authentication

A user is affected if their GitLab version is within the vulnerable ranges AND they have merge requests configured with visibility restricted to project members that are publicly accessible.

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.11.5 / 17.0.3 or later
Fixed in 16.11.517.0.3
Interim mitigation

Upgrade GitLab to version 16.11.5, 17.0.3, 17.1.1 or later to remediate the access control bypass on merge request title visibility.

Recommended fix High confidence

Upgrade to GitLab 16.11.5+, 17.0.3+, or 17.1.1+ (recommended: latest stable 17.x release)

  1. 1. Back up your GitLab instance data including database and repositories
  2. 2. Ensure you have a restore point in case of issues
  3. 3. Plan for downtime during the upgrade process
  4. 4. For GitLab installations using the official Omnibus package: Run 'sudo apt-get update && sudo apt-get install gitlab-ce' (or gitlab-ee for Enterprise Edition)
  5. 5. For source installations: Follow the upgrade path in the GitLab documentation for your specific installation method
  6. 6. After upgrade, verify that merge request titles set to 'Project members only' are no longer publicly visible
  7. 7. Test that the access control settings for merge requests work correctly
Caveat Standard GitLab upgrade considerations apply - review release notes for any configuration or database migration requirements

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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