dbcve.org
GitLabApplication

CVE-2024-4660

HIGH · 7.5 CVSS v3.1 Published 2024-09-12
Fix available
A fix is available. Upgrade to 17.1.7 / 17.2.5 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 starting from 11.2 before 17.1.7, all versions starting from 17.2 before 17.2.5, all versions starting from 17.3 before 17.3.2. It was possible for a guest to read the source code of a private project by using group templates.

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 EE allows guest users to bypass intended restrictions and read source code of private projects by leveraging group templates. The guest user exploits the template feature to access code they should not be authorized to view.

MitigationUpgrade GitLab to versions 17.1.7+, 17.2.5+, or 17.3.2+ to patch the access control flaw. Alternatively, restrict or disable guest user access to private projects until the upgrade 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:>= 11.2.0, < 17.1.7>= 17.2.0, < 17.2.5>= 17.3.0, < 17.3.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
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. Check your GitLab version
    Run `sudo gitlab-rake gitlab:env:info` or check the GitLab admin area at /admin/application_settings under the version information. Compare the installed version to the affected ranges: >= 11.2.0, < 17.1.7; >= 17.2.0, < 17.2.5; >= 17.3.0, < 17.3.2
    Affected if Your version falls within any of the affected ranges listed above
  2. Verify if guest users exist
    Navigate to Admin Area > Users and filter by guest role, or run: `sudo gitlab-rails console -e production` then `User.guest.count` to count guest users in your instance
    Affected if You have any guest users provisioned in your GitLab instance
  3. Check for private projects with guest access
    In the admin area, review projects set to Private visibility that have guest users added as members, or query via API: `GET /api/v4/projects?membership=true&min_access_level=10` (10 = guest level)
    Affected if Private projects exist where guest users have been granted any level of access

You are affected if your GitLab version is within the affected ranges AND you have guest users with access to private projects.

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.1.7 / 17.2.5 / 17.3.2 or later
Fixed in 17.1.717.2.517.3.2
Interim mitigation

Upgrade GitLab to versions 17.1.7+, 17.2.5+, or 17.3.2+ to patch the access control flaw. Alternatively, restrict or disable guest user access to private projects until the upgrade can be applied.

Recommended fix High confidence

17.1.7, 17.2.5, or 17.3.2 (depending on current branch)

  1. 1. Identify the current GitLab version by navigating to the GitLab admin area or running `gitlab-rake gitlab:env:info`
  2. 2. Determine the appropriate upgrade path based on current version (17.1.x → 17.1.7, 17.2.x → 17.2.5, or 17.3.x → 17.3.2)
  3. 3. Review GitLab upgrade documentation for your current version to ensure compatibility with the target version
  4. 4. Create a full backup of the GitLab instance using `gitlab-backup create`
  5. 5. Stop GitLab services with `gitlab-ctl stop`
  6. 6. Update GitLab using the appropriate package manager (omnibus) or source upgrade method
  7. 7. Reconfigure GitLab with `gitlab-ctl reconfigure`
  8. 8. Start GitLab services with `gitlab-ctl start`
Caveat Upgrading across multiple major versions (e.g., from 11.x to 17.x) may have significant breaking changes; review GitLab upgrade path documentation for intermediate steps

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-4660 — 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-4660 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