dbcve.org
GitLabApplication

CVE-2024-9631

HIGH · 7.5 CVSS v3.1 Published 2025-02-05
Fix available
A fix is available. Upgrade to 17.2.9 / 17.3.5 or later.
See remediation →
84/100
Remediation priority · High
Public exploit 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 13.6 prior to 17.2.9, starting from 17.3 prior to 17.3.5, and starting from 17.4 prior to 17.4.2, where viewing diffs of MR with conflicts can be slow.

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

A detailed technical summary for this CVE is being prepared.

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:>= 13.6.0, < 17.2.9>= 17.3.0, < 17.3.5>= 17.4.0, < 17.4.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
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

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.2.9 / 17.3.5 / 17.4.2 or later
Fixed in 17.2.917.3.517.4.2
Recommended fix High confidence

Upgrade to GitLab 17.4.2 or later (17.3.5+ if on 17.3.x branch, 17.2.9+ if on 17.2.x branch)

  1. 1. Back up your GitLab instance database and repositories before proceeding with the upgrade.
  2. 2. Review the GitLab upgrade path documentation for your current version to ensure compatibility.
  3. 3. For GitLab Omnibus installations: Run 'sudo gitlab-ctl stop' to stop services, then update the package using your system's package manager (e.g., 'sudo apt-get update && sudo apt-get install gitlab-ce' or 'sudo yum install gitlab-ce').
  4. 4. For Docker installations: Pull the fixed version image (e.g., 'docker pull gitlab/gitlab-ee:17.4.2') and recreate your container with the new image.
  5. 5. Run 'sudo gitlab-ctl reconfigure' after the package installation to apply configuration changes.
  6. 6. Verify the upgrade by checking GitLab version at /help (should show 17.4.2 or later) and ensure the application is functional.
  7. 7. Test viewing diffs of merge requests with conflicts to confirm the performance issue is resolved.
Caveat Major version upgrades (e.g., 16.x to 17.x) may require additional migration steps and have breaking changes; review the GitLab release notes for your upgrade path

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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