dbcve.org
GitLabApplication

CVE-2024-4557

MEDIUM · 6.5 CVSS v3.1 Published 2024-06-27
Fix available
A fix is available. Upgrade to 16.11.5 / 17.0.3 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 16.11.5, starting from 17.0 prior to 17.0.3, and starting from 17.1 prior to 17.1.1 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 · moderate confidence

This is a Denial of Service vulnerability in GitLab CE/EE where an attacker can cause resource exhaustion through the banzai pipeline component. The vulnerability affects multiple version branches and allows attackers to potentially overwhelm server resources.

MitigationUpgrade GitLab to version 16.11.5, 17.0.3, 17.1.1 or later to patch the resource exhaustion vulnerability in the banzai pipeline.

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.0, < 16.11.5>= 17.0.0, < 17.0.3= 17.1.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
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. Identify installed GitLab version
    Run `sudo gitlab-rake gitlab:version` or check `/opt/gitlab/embedded/service/gitlab-rails/VERSION` file
    Affected if Version is < 16.11.5 OR between 17.0.0 and 17.0.3 inclusive OR exactly 17.1.0
  2. Confirm GitLab edition
    Run `sudo gitlab-rake gitlab:env:info` and verify the edition is CE (Community Edition) or EE (Enterprise Edition)
    Affected if Edition is Community Edition or Enterprise Edition and version matches the affected range from step 1
  3. Verify banzai pipeline component is active
    Check if GitLab pipelines are enabled in the instance settings under Settings > Pipelines, or query the API endpoint `/api/v4/pipelines` to confirm pipeline functionality exists
    Affected if Pipelines are enabled and accessible - the banzai component is part of the pipeline processing system
  4. Review resource consumption logs
    Check GitLab logs at `/var/log/gitlab/gitlab-rails/production.log` for patterns of excessive pipeline processing or memory exhaustion, or monitor `gitlab-ctl tail` for unusual resource behavior
    Affected if Logs show repeated pipeline processing attempts causing high CPU/memory usage consistent with resource exhaustion

The environment is affected if the installed GitLab version falls within 16.11.5+, 17.0.0-17.0.3, or exactly 17.1.0 AND the banzai pipeline component is active on the instance.

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 16.11.5 / 17.0.3 or later
Fixed in 16.11.517.0.3
Interim mitigation

Upgrade GitLab to version 16.11.5, 17.0.3, 17.1.1 or later to patch the resource exhaustion vulnerability in the banzai pipeline.

Recommended fix High confidence

16.11.5 (for 16.x) or 17.1.1 (for 17.x)

  1. Identify current GitLab version using gitlab-rake gitlab:env:info
  2. For GitLab 16.x users: Upgrade to version 16.11.5 or later
  3. For GitLab 17.0.x users: Upgrade to version 17.0.3
  4. For GitLab 17.1.0 users: Upgrade to version 17.1.1
  5. After upgrade, verify GitLab is operational using gitlab-rake gitlab:check
  6. Monitor resource usage to confirm the DoS vector is mitigated
Caveat Patch releases (16.11.5, 17.0.3, 17.1.1) contain only security fixes with no expected breaking changes; major version upgrades from 16.x to 17.x may have breaking changes - review GitLab 17.0 release notes before upgrading

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

Fix this in GitLab Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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