dbcve.org
GitLabApplication

CVE-2024-8973

HIGH · 7.5 CVSS v3.1 Published 2025-05-09
Fix available
A fix is available. Upgrade to 17.9.8 / 17.10.6 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 CE/EE affecting all versions starting from 17.1 prior to 17.9.8, from 17.10 prior to 17.10.6, and from 17.11 prior to 17.11.2. It was possible to cause a DoS condition via GitHub import requests using a malicious crafted payload.

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 denial of service vulnerability exists in GitLab CE/EE allowing attackers to crash the application via malicious crafted payloads sent through the GitHub import feature. The vulnerability affects all versions from 17.1 through 17.9.8, 17.10 through 17.10.6, and 17.11 through 17.11.1.

MitigationUpgrade to GitLab versions 17.9.8, 17.10.6, or 17.11.2 or later. As a temporary mitigation, consider rate limiting or temporarily disabling the GitHub import functionality until the upgrade can be completed.

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.1.0, < 17.9.8>= 17.10.0, < 17.10.6>= 17.11.0, < 17.11.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

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 /opt/gitlab/version-manifest.txt, or view the version in the GitLab admin area under Help > Version
    Affected if The installed version is 17.1.0 or higher but lower than 17.9.8, OR 17.10.0 or higher but lower than 17.10.6, OR 17.11.0 or higher but lower than 17.11.2
  2. Verify GitHub import feature is accessible
    Navigate to any project and check if the GitHub import option appears at /import/github/new, or review the import_sources setting in gitlab.yml configuration file
    Affected if GitHub import is listed as an available import source and the GitLab version is in the affected range

The environment is affected if the GitLab version falls within 17.1.0 to 17.9.7, 17.10.0 to 17.10.5, or 17.11.0 to 17.11.1 AND the GitHub import feature is enabled and accessible to users

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.9.8 / 17.10.6 / 17.11.2 or later
Fixed in 17.9.817.10.617.11.2
Interim mitigation

Upgrade to GitLab versions 17.9.8, 17.10.6, or 17.11.2 or later. As a temporary mitigation, consider rate limiting or temporarily disabling the GitHub import functionality until the upgrade can be completed.

Recommended fix High confidence

Upgrade to GitLab 17.9.8, 17.10.6, or 17.11.2 (whichever corresponds to your current release branch)

  1. Identify the currently installed GitLab version using 'gitlab-rake gitlab:env:info' or checking /opt/gitlab/version-manifest.txt
  2. Determine the appropriate target version based on your current branch: if on 17.1-17.9.x, upgrade to 17.9.8; if on 17.10.x, upgrade to 17.10.6; if on 17.11.x, upgrade to 17.11.2
  3. Back up the GitLab database and repositories using 'gitlab-backup-create'
  4. Stop GitLab services with 'gitlab-ctl stop'
  5. Update the GitLab package using the standard package manager for your distribution (e.g., apt-get update && apt-get install gitlab-ce for Debian/Ubuntu, or yum install for RHEL/CentOS)
  6. Verify the new version is installed by running 'gitlab-rake gitlab:env:info'
  7. Restart GitLab services with 'gitlab-ctl start'
  8. Run 'gitlab-rake gitlab:check' to verify the installation is healthy
Caveat Standard GitLab upgrade considerations apply - review the upgrade path for your specific version and ensure compatibility with your runner and integration versions

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

Fix this in GitLab Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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