dbcve.org
GitLabApplication

CVE-2024-7803

HIGH · 7.5 CVSS v3.1 Published 2025-05-23
Fix available
A fix is available. Upgrade to 17.10.7 / 17.11.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
An issue has been discovered in GitLab CE/EE affecting all versions from 11.6 before 17.10.7, 17.11 before 17.11.3, and 18.0 before 18.0.1. A Discord webhook integration may cause DoS.

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

GitLab CE/EE contains a denial of service vulnerability in the Discord webhook integration feature. The issue affects all versions from 11.6 through the vulnerable versions (17.10.7, 17.11.3, 18.0.1), where specially crafted Discord webhook requests can cause the service to become unavailable.

MitigationUpgrade GitLab to version 17.10.7, 17.11.3, 18.0.1 or later. Alternatively, disable the Discord webhook integration until the patch can be applied.

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.6.0, < 17.10.7>= 17.11.0, < 17.11.3= 18.0.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 'gitlab-rake gitlab:env:info' from the GitLab server command line, or view the version in the web UI under Admin Area > Dashboard. Alternatively, check /opt/gitlab/embedded/lib/ruby/gems/*/gitlab/version.rb
    Affected if version falls within 11.6.0 to 17.10.6, 17.11.0 to 17.11.2, or is exactly 18.0.0 (not fixed versions 17.10.7, 17.11.3, 18.0.1 or later)
  2. Check if Discord webhook integration is enabled
    Navigate to Admin Area > Settings > Integrations in the GitLab web UI, locate the Discord Webhooks integration, and verify whether it is active. Or query the integrations API endpoint withcurl -s --header "PRIVATE-TOKEN: <your-token>" "https://gitlab.example.com/api/v4/integrations?active=true&service=discord"
    Affected if Discord webhook integration is enabled and configured with a target webhook URL
  3. Audit project-level Discord webhooks
    In each project, go to Settings > Webhooks and look for webhooks with Discord service type, or query the database directly if you have psql access: SELECT id, project_id, url FROM webhooks WHERE service = 'discord' AND active = true;
    Affected if any project has an active Discord-type webhook configured

Environment is affected only if running a vulnerable GitLab version AND the Discord webhook integration is enabled with an active webhook URL, exposing the service to specially crafted Discord webhook requests.

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.10.7 / 17.11.3 or later
Fixed in 17.10.717.11.3
Interim mitigation

Upgrade GitLab to version 17.10.7, 17.11.3, 18.0.1 or later. Alternatively, disable the Discord webhook integration until the patch can be applied.

Recommended fix High confidence

17.10.7, 17.11.3, or 18.0.1 (depending on your current version branch)

  1. Back up your GitLab instance database and repositories before proceeding
  2. Identify your current GitLab version in the GitLab Admin Area under the Help section or by running `gitlab-rake gitlab:env:info`
  3. If running 17.10.x, upgrade to version 17.10.7 or later
  4. If running 17.11.x, upgrade to version 17.11.3 or later
  5. If running 18.0.0, upgrade to version 18.0.1 or later
  6. If running an earlier version (11.6.0 to 17.9.x), upgrade first to a 17.10.x release (e.g., 17.10.7) before upgrading to later major versions
  7. Follow the official GitLab upgrade documentation for your installation method (omnibus, source, or Docker)
  8. After upgrade, verify the Discord webhook integration functionality works as expected

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

Fix this in GitLab Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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