dbcve.org
GitLabApplication

CVE-2024-10307

MEDIUM · 5.5 CVSS v3.1 Published 2025-03-28
Fix available
A fix is available. Upgrade to 17.8.6 / 17.9.3 or later.
See remediation →
58/100
Remediation priority · Elevated
No privileges

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/CE affecting all versions from 12.10 before 17.8.6, 17.9 before 17.9.3, and 17.10 before 17.10.1. A maliciously crafted file can cause uncontrolled CPU consumption when viewing the associated merge request.

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 denial-of-service vulnerability in GitLab allows a maliciously crafted file to trigger uncontrolled CPU consumption when a user views the associated merge request. The vulnerability stems from insufficient handling of specially crafted file content during merge request rendering, leading to resource exhaustion.

MitigationUpgrade GitLab to version 17.8.6, 17.9.3, 17.10.1 or later. As a temporary workaround, restrict merge request creation to trusted users until the upgrade can be performed.

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:>= 12.10.0, < 17.8.6>= 17.9.0, < 17.9.3= 17.10.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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

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 installed GitLab version
    Run `sudo gitlab-rake gitlab:env:info` or check the GitLab admin panel under Help > Version. Alternatively, check the package version with `dpkg -l | grep gitlab-ee` (Debian/Ubuntu) or `rpm -qa | grep gitlab` (RHEL/CentOS).
    Affected if Version output is empty or cannot be retrieved, preventing version-based determination.
  2. Compare version against affected ranges
    Locate the version number from the previous step. Compare it to these affected ranges: 12.10.0 to 17.8.5 (inclusive), 17.9.0 to 17.9.2 (inclusive), or exactly 17.10.0.
    Affected if Installed version falls within any of these ranges: >= 12.10.0 and < 17.8.6, OR >= 17.9.0 and < 17.9.3, OR equals 17.10.0.
  3. Check merge request creation permissions
    In GitLab admin area, go to Settings > General > Visibility and access controls. Review who can create merge requests (project members, developers, or external users).
    Affected if Untrusted or external users can create or submit merge requests to any project.
  4. Identify active merge requests with external content
    Review recent merge requests in projects. Check for files from external contributors or repositories that may contain specially crafted content designed to trigger CPU exhaustion during rendering.
    Affected if Merge requests from untrusted sources exist and contain arbitrary file attachments.

You are affected if your GitLab version falls within the vulnerable ranges AND merge requests from untrusted sources can be created or viewed in your environment.

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.9.3 or later
Fixed in 17.8.617.9.3
Interim mitigation

Upgrade GitLab to version 17.8.6, 17.9.3, 17.10.1 or later. As a temporary workaround, restrict merge request creation to trusted users until the upgrade can be performed.

Recommended fix High confidence

17.8.6, 17.9.3, 17.10.1, or later (recommended: latest stable 17.x release)

  1. 1. Back up your GitLab instance data and configuration before upgrading
  2. 2. Identify your current GitLab version by running `gitlab-rake gitlab:env:info` or checking the UI at /help
  3. 3. For GitLab installations: Follow the official upgrade path for your installation method (Omnibus, source, or Helm chart)
  4. 4. For Omnibus: Run `apt-get update && apt-get install gitlab-ee` (Debian/Ubuntu) or `yum install gitlab-ee` (RHEL/CentOS)
  5. 5. After installation, run `gitlab-ctl reconfigure` to apply configuration changes
  6. 6. Verify the upgrade succeeded by checking the version at /help or running `gitlab-rake gitlab:env:info`
  7. 7. Confirm the new version is 17.8.6, 17.9.3, 17.10.1, or later
Caveat Review GitLab upgrade guides for any required migration steps between major versions; always test upgrades in a staging environment first

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
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
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,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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