dbcve.org
GitLabApplication

CVE-2024-1736

MEDIUM · 6.5 CVSS v3.1 Published 2024-06-12
Fix available
A fix is available. Upgrade to 16.10.7 / 16.11.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
An issue has been discovered in GitLab CE/EE affecting all versions prior to 16.10.7, starting from 16.11 prior to 16.11.4, and starting from 17.0 prior to 17.0.2. A vulnerability in GitLab's CI/CD pipeline editor could allow for denial of service attacks through maliciously crafted configuration files.

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 exists in GitLab's CI/CD pipeline editor component. Attackers can exploit this by submitting maliciously crafted .gitlab-ci.yml configuration files that cause excessive resource consumption or processing failures, rendering the pipeline editor unavailable.

MitigationUpgrade GitLab to version 16.10.7, 16.11.4, or 17.0.2 or later to patch this vulnerability. Until patched, restrict CI/CD configuration file access to trusted users only.

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:< 16.10.7>= 16.11.0, < 16.11.4>= 17.0.0, < 17.0.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. Determine your GitLab version
    Log into GitLab as an administrator, go to Admin Area > Settings > About, or run `sudo gitlab-rake gitlab:env:info` on the server to retrieve the installed version number
    Affected if The displayed version falls within < 16.10.7, or >= 16.11.0 to < 16.11.4, or >= 17.0.0 to < 17.0.2
  2. Verify CI/CD pipeline editor is accessible
    Navigate to any project and check if the CI/CD Pipeline Editor (accessible via Project > Build > Pipeline editor) is available and functional
    Affected if The pipeline editor interface loads and is usable, indicating the component is enabled
  3. Confirm user access to CI/CD configuration
    Navigate to Project > Repository > Files and locate .gitlab-ci.yml, or go to CI/CD Settings > Pipeline editor to see who can modify pipeline configurations
    Affected if Untrusted or unauthenticated users have the ability to create or modify .gitlab-ci.yml files in any project
  4. Check for pipeline processing issues
    Review recent pipeline jobs in Project > Build > Pipelines for signs of excessive resource consumption, timeouts, or failed processing
    Affected if Pipelines are failing with resource-related errors or taking unusually long to process simple configurations

Your environment is affected if the GitLab version is lower than 16.10.7, between 16.11.0-16.11.3, or between 17.0.0-17.0.1 AND untrusted users can access the CI/CD pipeline editor to submit .gitlab-ci.yml files.

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.10.7 / 16.11.4 / 17.0.2 or later
Fixed in 16.10.716.11.417.0.2
Interim mitigation

Upgrade GitLab to version 16.10.7, 16.11.4, or 17.0.2 or later to patch this vulnerability. Until patched, restrict CI/CD configuration file access to trusted users only.

Recommended fix High confidence

Upgrade to GitLab 17.0.2 (or minimum 16.10.7/16.11.4 depending on your current version branch)

  1. 1. Back up your GitLab instance data and configuration before proceeding with the upgrade
  2. 2. Review GitLab's upgrade path documentation to ensure compatibility with your current version
  3. 3. Plan maintenance window as upgrade will require service interruption
  4. 4. Upgrade GitLab to version 17.0.2 (or at minimum 16.10.7 or 16.11.4 depending on your branch)
  5. 5. After upgrade, verify the CI/CD pipeline editor functionality is working correctly
  6. 6. Test that legitimate .gitlab-ci.yml files parse correctly
  7. 7. Monitor system performance to confirm DoS vulnerability is mitigated
Caveat Major version upgrades may require database migrations; review GitLab 17.0 release notes for any configuration or breaking changes 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-1736 — 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-1736 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