dbcve.org
GitLabApplication

CVE-2024-5423

MEDIUM · 6.5 CVSS v3.1 Published 2024-08-08
Fix available
A fix is available. Upgrade to 17.0.6 / 17.1.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
Multiple Denial of Service (DoS) conditions has been discovered in GitLab CE/EE affecting all versions starting from 1.0 prior to 17.0.6, starting from 17.1 prior to 17.1.4, and starting from 17.2 prior to 17.2.2 which allowed an attacker to cause resource exhaustion via banzai pipeline.

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

GitLab CE/EE versions prior to 17.0.6, 17.1.4, and 17.2.2 contain multiple denial-of-service vulnerabilities in the banzai pipeline component. Attackers can exploit these to cause resource exhaustion by sending specially crafted requests through the pipeline system, potentially rendering the GitLab instance unresponsive.

MitigationUpgrade GitLab to version 17.0.7, 17.1.5, 17.2.3, or later to patch the banzai pipeline DoS vulnerabilities.

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:>= 1.0, < 17.0.6>= 17.1.0, < 17.1.4>= 17.2.0, < 17.2.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
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. Confirm GitLab is installed
    Check for GitLab installation by looking for common installation directories or using package managers. On Linux with Omnibus: ls /opt/gitlab. Or check for gitlab-rake command availability.
    Affected if GitLab is not present on the system, this CVE does not apply.
  2. Retrieve the installed GitLab version
    Run 'gitlab-rake gitlab:env:info' or check the version file at /opt/gitlab/version for Omnibus installations. For source installations, check the version file in the GitLab directory.
    Affected if Unable to determine the version, cannot assess CVE impact.
  3. Compare version against affected ranges
    Check if the installed version falls into any of these ranges: < 17.0.6, >= 17.1.0 and < 17.1.4, or >= 17.2.0 and < 17.2.2.
    Affected if The installed version is within any of these ranges (1.0 to 17.0.5, 17.1.0 to 17.1.3, or 17.2.0 to 17.2.1).
  4. Verify banzai pipeline component is in use
    The banzai pipeline is part of GitLab CI/CD core functionality and is enabled by default. Check for CI/CD pipelines configured at Admin Area > Pipelines Settings, or review .gitlab-ci.yml files in repositories.
    Affected if CI/CD pipelines are configured and the GitLab version is vulnerable, the system is affected by this DoS vulnerability.

A system is affected if it runs a vulnerable GitLab version (< 17.0.6, 17.1.0-17.1.3, or 17.2.0-17.2.1) and has CI/CD pipeline functionality enabled, which is the default state.

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.0.6 / 17.1.4 / 17.2.2 or later
Fixed in 17.0.617.1.417.2.2
Interim mitigation

Upgrade GitLab to version 17.0.7, 17.1.5, 17.2.3, or later to patch the banzai pipeline DoS vulnerabilities.

Recommended fix High confidence

17.0.6, 17.1.4, 17.2.2 or later

  1. Back up the GitLab instance database and configuration files before upgrading
  2. Review GitLab's official upgrade documentation for your current version to the target version
  3. Upgrade to one of the fixed releases: 17.0.6, 17.1.4, or 17.2.2 (or a later stable release)
  4. After upgrade, verify the GitLab service is running and accessible
  5. Confirm the banzai pipeline resource exhaustion issue is resolved by testing pipeline execution
Caveat When upgrading across major versions (e.g., 16.x to 17.x), review GitLab's release notes for breaking changes and database migration requirements

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
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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