dbcve.org
GitLabApplication

CVE-2024-4025

HIGH · 7.5 CVSS v3.1 Published 2025-06-20
Fix available
A fix is available. Upgrade to 16.11.5 / 17.0.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 has been discovered in GitLab CE/EE affecting all versions from 7.10 prior before 16.11.5, version 17.0 before 17.0.3, and 17.1 before 17.1.1. It is possible for an attacker to cause a denial of service using a crafted markdown page.

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 an attacker can cause a DoS condition by submitting a crafted markdown page. The vulnerability affects all versions from 7.10 prior to 16.11.5, versions 17.0 prior to 17.0.3, and versions 17.1 prior to 17.1.1.

MitigationUpgrade GitLab to version 16.11.5, 17.0.3, 17.1.1 or later to patch the vulnerability. If immediate patching is not possible, consider restricting markdown rendering capabilities or implementing rate limiting on markdown processing endpoints.

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:>= 7.10.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
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. Determine installed GitLab version
    Run 'sudo gitlab-rake gitlab:env:info' or check the version file in your GitLab installation directory (commonly at /opt/gitlab/embedded/service/gitlab-rails/VERSION or /var/opt/gitlab/gitlab-rails/VERSION). Alternatively, access the Admin Area dashboard in the web UI under the 'Health Check' or 'Version' section.
    Affected if The installed version falls within any of these ranges: 7.10.0 to 16.11.4 inclusive, 17.0.0 to 17.0.2 inclusive, or exactly 17.1.0.
  2. Confirm markdown rendering is accessible
    Verify that the GitLab instance has markdown rendering enabled for user-facing features such as Issues, Merge Requests, Comments, or Wikis. This is typically enabled by default. Check by viewing any Issue or Merge Request to confirm markdown content renders properly.
    Affected if Markdown rendering is enabled (default state). The vulnerability is triggered when a crafted markdown page is submitted, which requires markdown processing to be available.
  3. Check for recent markdown submission activity
    Review GitLab logs for markdown processing activity. Logs are typically located at /var/log/gitlab/gitlab-rails/production.log or can be accessed via 'sudo gitlab-ctl tail gitlab-rails' in standard installations. Search for entries related to markdown rendering or note any unusual spikes in processing.
    Affected if There is evidence of markdown content being processed, particularly from unauthenticated or external sources if that configuration is allowed.

You are affected if your GitLab version is 7.10.0 through 16.11.4, 17.0.0 through 17.0.2, or exactly 17.1.0, and markdown rendering is enabled (the default configuration).

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 vulnerability. If immediate patching is not possible, consider restricting markdown rendering capabilities or implementing rate limiting on markdown processing endpoints.

Recommended fix High confidence

16.11.5 (16.x) / 17.0.3 (17.0.x) / 17.1.1 (17.1.x) - recommended: latest stable 17.x release

  1. Back up your GitLab instance data and configuration before proceeding
  2. Schedule a maintenance window for the upgrade
  3. Upgrade GitLab to a fixed version: 16.11.5 or later for 16.x, 17.0.3 or later for 17.0.x, or 17.1.1 or later for 17.1.x
  4. Run gitlab-ctl reconfigure after the package upgrade completes
  5. Verify GitLab services are running and the instance is accessible
  6. Test markdown rendering functionality to confirm the vulnerability is remediated
Caveat Review GitLab upgrade notes for breaking changes between your current version and target version; major version upgrades may require additional migration steps

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

Fix this in GitLab Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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