dbcve.org
GitLabApplication

CVE-2024-1963

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 starting from 8.4 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 Asana integration allowed an attacker to potentially cause a regular expression denial of service by sending specially crafted requests.

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's Asana integration across versions 8.4 through 16.10.7, 16.11.0-16.11.4, and 17.0.0-17.0.2. Attackers can send specially crafted requests that cause excessive regex processing, leading to service degradation or unavailability.

MitigationUpgrade GitLab to version 16.10.7, 16.11.4, 17.0.2 or later to patch the ReDoS vulnerability in the Asana integration.

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:>= 8.4, < 16.10.7>= 16.11.0, < 16.11.4>= 17.0, <= 17.0.2>= 17.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 installed GitLab version
    Run `gitlab-rake gitlab:env:info` or check the GitLab admin panel under the Help section to find the exact version number
    Affected if The version falls within 8.4 to <16.10.7, 16.11.0 to <16.11.4, or 17.0.0 to <=17.0.2
  2. Check if Asana integration is in use
    Navigate to GitLab admin settings or project-level integrations page and verify whether the Asana integration has been enabled or configured
    Affected if The Asana integration is enabled or has been configured with an Asana project link
  3. Verify Asana integration is reachable via web requests
    Confirm that the Asana integration endpoints are exposed and accessible to external attackers, typically at /api/v4/integrations/asana or similar paths
    Affected if The integration endpoints are publicly accessible without additional network segmentation

You are affected if your GitLab version is within the vulnerable ranges AND the Asana integration is enabled or configured 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 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, 17.0.2 or later to patch the ReDoS vulnerability in the Asana integration.

Recommended fix High confidence

16.10.7 (or 16.11.4 or 17.0.2 depending on your major version branch)

  1. 1. Back up your GitLab instance data before proceeding with the upgrade.
  2. 2. Identify your current GitLab version by navigating to the GitLab admin area or running `gitlab-rake gitlab:env:info`.
  3. 3. For GitLab versions 8.4 through 16.10.x: upgrade to version 16.10.7 or later.
  4. 4. For GitLab versions 16.11.x: upgrade to version 16.11.4 or later.
  5. 5. For GitLab version 17.0.x: upgrade to version 17.0.2 or later (17.0.3 or later recommended).
  6. 6. After upgrade, verify the Asana integration functionality is working correctly.
  7. 7. Monitor system performance to confirm the ReDoS vulnerability is mitigated.
Caveat Standard GitLab upgrade considerations apply - review release notes for any configuration or database migration requirements

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-1963 — 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-1963 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