dbcve.org
GitLabApplication

CVE-2024-4210

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
A Denial of Service (DoS) condition has been discovered in GitLab CE/EE affecting all versions starting with 12.6 before 17.0.6, 17.1 prior to 17.1.4, and 17.2 prior to 17.2.2. It is possible for an attacker to cause a denial of service using crafted adoc 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 · high confidence

A Denial of Service vulnerability exists in GitLab CE/EE where crafted AsciiDoc (.adoc) files can trigger a DoS condition. The vulnerability affects all versions from 12.6 through the unpatched versions of 17.0.x, 17.1.x, and 17.2.x.

MitigationUpgrade GitLab to version 17.0.6, 17.1.4, 17.2.2 or later to remediate this 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:>= 12.6.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
    Run `sudo gitlab-rake gitlab:version` or check /opt/gitlab/VERSION file to determine the installed GitLab version
    Affected if The version falls within 12.6.0 to 17.0.5, 17.1.0 to 17.1.3, or 17.2.0 to 17.2.1
  2. Verify AsciiDoc rendering is enabled
    Check if AsciiDoc gem is loaded in GitLab: run `sudo gitlab-rails runner "puts Git::Asciidoc.asciidoc_gem_available?"`
    Affected if Asciidoc gem is available and GitLab can process .adoc files
  3. Look for .adoc files in repositories
    Search for .adoc files in GitLab repositories using API or web interface, or check common paths like project README files
    Affected if Any .adoc files exist in accessible repositories that could be rendered by GitLab

You are affected if your GitLab version is within the vulnerable ranges (12.6.0-17.0.5, 17.1.0-17.1.3, or 17.2.0-17.2.1) and AsciiDoc files can be processed in your environment.

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 to remediate this vulnerability.

Recommended fix High confidence

17.0.6, 17.1.4, or 17.2.2 (or latest 17.x stable)

  1. 1. Backup your GitLab instance database and repositories before proceeding with the upgrade
  2. 2. Determine your current GitLab version by running `gitlab-rake gitlab:env:info` or checking the GitLab admin area
  3. 3. Choose the appropriate upgrade path based on your current version: if on 12.6.x-16.x, upgrade to 17.0.6 first then to latest 17.x; if on 17.0.x, upgrade to 17.0.6; if on 17.1.x, upgrade to 17.1.4; if on 17.2.0-17.2.1, upgrade to 17.2.2
  4. 4. For self-managed instances, follow the official upgrade documentation at https://docs.gitlab.com/ee/update/ to upgrade to your chosen fixed version
  5. 5. For GitLab SaaS (gitlab.com), no action required as the vendor handles updates
  6. 6. After upgrade, verify the version by running `gitlab-rake gitlab:env:info` and confirm it shows a fixed version (17.0.6, 17.1.4, 17.2.2, or later)
Caveat Major version upgrades (e.g., 12.x to 17.x) may require intermediate upgrades and have significant changes; review GitLab upgrade path documentation for required intermediate steps

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

Fix this in GitLab Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,180
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,488.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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