dbcve.org
GitLabApplication

CVE-2024-9512

MEDIUM · 5.9 CVSS v3.1 Published 2025-06-12
Fix available
A fix is available. Upgrade to 17.10.8 / 17.11.4 or later.
See remediation →
68/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 has been discovered in GitLab EE affecting all versions prior to 17.10.8, 17.11 prior to 17.11.4, and 18.0 prior to 18.0.2. It may have been possible for private repository to be cloned in case of race condition when a secondary node is out of sync.

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 · moderate confidence

A race condition in GitLab EE allows private repositories to be cloned when a secondary node is out of sync with the primary. During the synchronization window, an attacker could potentially access private repositories before the access controls are properly enforced across nodes.

MitigationUpgrade GitLab EE to version 17.10.8, 17.11.4, 18.0.2 or later. Ensure proper node synchronization is maintained and monitor for any anomalous repository access during failover scenarios.

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.10.8>= 17.11.0, < 17.11.4>= 18.0.0, < 18.0.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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:H/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. Confirm GitLab edition is EE (Enterprise Edition)
    Run `grep -E '^gitlab-ee' /opt/gitlab/version-manifest.txt` or check the license file at `/opt/gitlab/license.rb` for 'enterprise' indicators. Alternatively, check the admin area UI for the GitLab edition.
    Affected if Running GitLab CE (Community Edition) is not affected; only GitLab EE is vulnerable.
  2. Determine installed GitLab version
    Run `gitlab-rake gitlab:version` or check `/opt/gitlab/embedded/service/gitlab-rails/VERSION` file to obtain the exact installed version.
    Affected if Version falls in < 17.10.8, >= 17.11.0 and < 17.11.4, or >= 18.0.0 and < 18.0.2.
  3. Verify multi-node HA deployment exists
    Check for the presence of multiple GitLab nodes by reviewing the gitlab.rb configuration file at `/etc/gitlab/gitlab.rb` for `gitlab_rails['gitlab_shell_ssh_port']` entries across nodes, or query the database for multiple node records in the `geo_nodes` table if Geo is enabled, or check load balancer configurations.
    Affected if This vulnerability only affects environments with primary and secondary nodes; single-node installations are not impacted.
  4. Check node synchronization status
    On secondary nodes, run `git Geo status` or query the database for replication lag in the `geo_event_log` table to identify if nodes are out of sync. Also check `gitlab-rake geo:status` for sync state.
    Affected if If secondary nodes show replication lag, delayed sync, or out-of-sync status during normal operation, the race condition window exists.
  5. Review repository access logs for anomalous private repo clones
    Search Rails logs at `/var/log/gitlab/gitlab-rails/production_json.log` for `repository_cloned` events where the user accessing should not have permission, or check the `audit_events` table for unauthorized repository access patterns.
    Affected if Any private repository access attempts occurring during known synchronization windows or from nodes reporting out-of-sync status indicate potential exploitation.

A user is affected if running GitLab EE in a multi-node configuration with a version in the affected ranges, where secondary nodes can become temporarily out of sync with the primary, allowing unauthorized private repository access.

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.10.8 / 17.11.4 / 18.0.2 or later
Fixed in 17.10.817.11.418.0.2
Interim mitigation

Upgrade GitLab EE to version 17.10.8, 17.11.4, 18.0.2 or later. Ensure proper node synchronization is maintained and monitor for any anomalous repository access during failover scenarios.

Recommended fix High confidence

18.0.2 (or 17.11.4 if staying on 17.11, or 17.10.8 if staying on 17.10)

  1. Review the current GitLab version using `gitlab-rake gitlab:env:info`
  2. Backup your GitLab instance including database and repositories
  3. For installations using OMU (Omnibus), run: `sudo apt-get update && sudo apt-get install gitlab-ee` (Debian/Ubuntu) or `sudo yum install gitlab-ee` (RHEL/CentOS)
  4. For installations using source, follow the upgrade documentation at https://docs.gitlab.com/ee/update/
  5. After upgrade, verify the new version with `gitlab-rake gitlab:env:info`
  6. Test that private repository cloning works correctly in a HA/clustered setup

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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