dbcve.org
GitLabApplication

CVE-2024-3114

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
An issue was discovered in GitLab CE/EE affecting all versions starting from 11.10 prior to 17.0.6, 17.1 prior to 17.1.4, and 17.2 prior to 17.2.2, with the processing logic for parsing invalid commits can lead to a regular expression DoS attack on the server.

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 regular expression denial of service (ReDoS) vulnerability exists in GitLab CE/EE's commit parsing logic. When processing invalid commits, the regex engine can be forced into excessive backtracking, causing server resource exhaustion and DoS.

MitigationUpgrade GitLab to version 17.0.6, 17.1.4, 17.2.2 or later. This is a patch-update only; no configuration changes required.

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:>= 11.10.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. Check GitLab version via command line
    Run `sudo gitlab-rake gitlab:env:info` or `gitlab --version` to retrieve the installed GitLab version
    Affected if The displayed version falls within any of these ranges: 11.10.0 to 17.0.5, 17.1.0 to 17.1.3, or 17.2.0 to 17.2.1
  2. Verify GitLab package version from filesystem
    If installed via Omnibus package, run `cat /opt/gitlab/version` or check the RPM/DEB package version with `dpkg -l | grep gitlab-ee` or `rpm -qa | grep gitlab`
    Affected if The package version matches the vulnerable ranges listed above
  3. Confirm commit processing is active
    GitLab's commit parsing is a core service enabled by default. No configuration check needed unless GitLab services are explicitly stopped
    Affected if GitLab instance is operational and processing repository data (the vulnerability triggers on invalid commit handling)

You are affected if your GitLab installation version is 11.10.0 through 17.0.5, 17.1.0 through 17.1.3, or 17.2.0 through 17.2.1, and the instance is actively processing commits

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.6, 17.1.4, 17.2.2 or later. This is a patch-update only; no configuration changes required.

Recommended fix High confidence

17.0.6, 17.1.4, or 17.2.2 (depending on current major version)

  1. 1. Back up your GitLab instance data before proceeding with the upgrade.
  2. 2. Identify your current GitLab version by navigating to the Admin Area > Settings > General page.
  3. 3. For installations on GitLab 17.0.x: upgrade to version 17.0.6
  4. 4. For installations on GitLab 17.1.x: upgrade to version 17.1.4
  5. 5. For installations on GitLab 17.2.x or 17.3.x: upgrade to version 17.2.2 or later
  6. 6. For older installations (11.10.0 - 16.x): plan an upgrade path to reach one of the fixed versions (17.0.6, 17.1.4, or 17.2.2)
  7. 7. Follow the official GitLab upgrade documentation for your installation method (Omnibus, source, or Helm chart)
  8. 8. Verify the upgrade was successful and the GitLab instance is operational
Caveat Review GitLab release notes for your target version as there may be required database migrations and compatibility considerations

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

Fix this in GitLab Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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