dbcve.org
GitLabApplication

CVE-2024-11828

HIGH · 7.5 CVSS v3.1 Published 2024-11-26
Fix available
A fix is available. Upgrade to 17.4.5 / 17.5.3 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
A denial of service (DoS) condition was discovered in GitLab CE/EE affecting all versions from 13.2.4 before 17.4.5, 17.5 before 17.5.3, and 17.6 before 17.6.1. By leveraging this vulnerability an attacker could create a DoS condition by sending crafted API calls. This was a regression of an earlier patch.

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 CE/EE allows attackers to crash the service via crafted API calls. This affects all versions from 13.2.4 through the vulnerable ranges (17.4.x before 17.4.5, 17.5.x before 17.5.3, and 17.6.x before 17.6.1). The flaw is a regression of a previously patched issue.

MitigationUpgrade GitLab to version 17.4.5, 17.5.3, 17.6.1 or later to resolve this DoS vulnerability.

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:>= 13.2.4, < 17.4.5>= 17.5.0, < 17.5.3= 17.6.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
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. Check GitLab version via CLI
    Run `gitlab-ctl version` or `gitlab-rake gitlab:env:info` on the GitLab server to retrieve the installed version number
    Affected if the reported version falls within 13.2.4 to 17.4.4, 17.5.0 to 17.5.2, or equals 17.6.0
  2. Check GitLab version via API
    Send a GET request to the `/api/v4/version` endpoint on your GitLab instance (e.g., `curl https://your-gitlab-instance/api/v4/version`)
    Affected if the version field in the JSON response matches the affected ranges listed above
  3. Check GitLab version via web UI
    Log into the GitLab web interface and navigate to Help > About, or check the Admin Area > Settings > General page for the version information
    Affected if the displayed version is within the vulnerable ranges
  4. Verify API accessibility
    Confirm your GitLab instance exposes API endpoints (e.g., test `curl -I https://your-gitlab-instance/api/v4/version`)
    Affected if API endpoints are accessible and the version check above shows a vulnerable release

You are affected if your installed GitLab version is 13.2.4 through 17.4.4, 17.5.0 through 17.5.2, or exactly 17.6.0, and your instance has accessible API endpoints.

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.4.5 / 17.5.3 or later
Fixed in 17.4.517.5.3
Interim mitigation

Upgrade GitLab to version 17.4.5, 17.5.3, 17.6.1 or later to resolve this DoS vulnerability.

Recommended fix High confidence

Upgrade to GitLab 17.4.5, 17.5.3, 17.6.1 or later (recommended: latest stable 17.x release)

  1. 1. Back up your GitLab instance data and configuration before proceeding
  2. 2. Plan a maintenance window as upgrade may require downtime
  3. 3. For GitLab installations using Omnibus (package): Run 'gitlab-ctl upgrade' or download and install the appropriate package from gitlab.com
  4. 4. For installations from source: Pull the latest tags from gitlabhq and follow upgrade documentation
  5. 5. Verify the upgrade completed successfully by checking GitLab version (Admin Area > Settings > General)
  6. 6. Test that API endpoints are functioning normally
  7. 7. Monitor system performance to confirm DoS condition is resolved
Caveat No breaking changes typically expected for DoS vulnerability patches; standard version upgrade procedures apply

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
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
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,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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