dbcve.org
GitLabApplication

CVE-2024-8041

MEDIUM · 6.5 CVSS v3.1 Published 2024-08-22
Fix available
A fix is available. Upgrade to 17.1.6 / 17.2.4 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
A Denial of Service (DoS) issue has been discovered in GitLab CE/EE affecting all versions prior to 17.1.6, 17.2 prior to 17.2.4, and 17.3 prior to 17.3.1. A denial of service could occur upon importing a maliciously crafted repository using the GitHub importer.

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 where importing a maliciously crafted repository through the GitHub importer can cause the service to become unavailable. The vulnerability affects all versions prior to 17.1.6, versions prior to 17.2.4 in the 17.2 branch, and versions prior to 17.3.1 in the 17.3 branch.

MitigationUpgrade GitLab to version 17.1.6, 17.2.4, 17.3.1 or later to remediate this vulnerability. Consider restricting or validating GitHub repository imports until the patch is 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:< 17.1.6>= 17.2.0, < 17.2.4>= 17.3.0, < 17.3.1

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 your GitLab version
    Run `sudo gitlab-rake gitlab:env:info` or check the GitLab UI at Admin Area > Settings > General > Metrics and profiling. Look for the version number in the output.
    Affected if The installed version is less than 17.1.6, OR between 17.2.0 and 17.2.3 inclusive, OR between 17.3.0 and 17.3.0 inclusive.
  2. Check if GitHub importer is enabled
    Navigate to Admin Area > Settings > Import and export (or /admin/application_settings/import_and_export_settings) and verify whether GitHub import is allowed in the Import sources section.
    Affected if GitHub import is enabled and the GitLab version falls within the affected ranges.
  3. Review recent import activity logs
    Check GitLab logs for entries containing 'github' and 'import' around the timeframe of potential exploitation. Logs are typically in /var/log/gitlab/gitlab-rails/production.log or accessible via `sudo gitlab-ctl tail` for recent activity.
    Affected if Logs show successful or attempted GitHub imports and the GitLab version is affected.

You are affected if your GitLab version is below 17.1.6, between 17.2.0-17.2.3, or between 17.3.0-17.3.0, AND the GitHub importer feature is enabled or has been used.

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.6 / 17.2.4 / 17.3.1 or later
Fixed in 17.1.617.2.417.3.1
Interim mitigation

Upgrade GitLab to version 17.1.6, 17.2.4, 17.3.1 or later to remediate this vulnerability. Consider restricting or validating GitHub repository imports until the patch is applied.

Recommended fix High confidence

17.1.6, 17.2.4, or 17.3.1 (choose based on your current branch)

  1. 1. Back up your GitLab instance database and repositories before starting the upgrade.
  2. 2. Review the GitLab upgrade documentation for your specific installation method (Omnibus, source, etc.).
  3. 3. Ensure your system meets the requirements for the target version.
  4. 4. For GitLab Omnibus: Stop GitLab services, run the package manager upgrade command (e.g., apt-get update && apt-get install gitlab-ce or yum install gitlab-ce), then reconfigure and restart.
  5. 5. For source installations: Pull the latest code from the GitLab repository, install dependencies, run database migrations, and restart the application.
  6. 6. Verify the upgrade was successful by checking the GitLab version in the admin area or via command line.
  7. 7. Test the GitHub importer functionality to confirm the vulnerability is resolved.
Caveat GitLab upgrades may introduce breaking changes; review the changelog for your target version before upgrading

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

Fix this in GitLab Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
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,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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