dbcve.org
GitLabApplication

CVE-2024-8648

MEDIUM · 6.1 CVSS v3.1 Published 2024-11-14
Fix available
A fix is available. Upgrade to 17.3.7 / 17.4.4 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 16 before 17.3.7, 17.4 before 17.4.4, and 17.5 before 17.5.2. The vulnerability could allow an attacker to inject malicious JavaScript code in Analytics Dashboards through a specially crafted URL.

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

This is a stored Cross-Site Scripting (XSS) vulnerability in GitLab CE/EE affecting versions 16.x through 17.5.x (before patches). Attackers can inject malicious JavaScript code into Analytics Dashboards via a specially crafted URL, potentially allowing session hijacking or actions on behalf of authenticated users.

MitigationUpgrade GitLab to version 17.3.7, 17.4.4, 17.5.2 or later. If immediate upgrading is not possible, restrict access to Analytics Dashboards features pending the patch.

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:>= 16.0.0, < 17.3.7>= 17.4.0, < 17.4.4>= 17.5.0, < 17.5.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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

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:version` or check the GitLab admin area at /help for the version number
    Affected if Version falls within >= 16.0.0, < 17.3.7 OR >= 17.4.0, < 17.4.4 OR >= 17.5.0, < 17.5.2
  2. Verify Analytics Dashboards module is accessible
    Check if users have access to Analytics Dashboards feature by navigating to the sidebar: Analytics > Dashboards or attempting to access /-/analytics/dashboards
    Affected if Analytics Dashboards feature is enabled and accessible to authenticated users
  3. Review Analytics Dashboards for suspicious content
    Inspect any saved or shared Analytics Dashboards for unexpected script tags, event handlers, or encoded payloads in dashboard names, descriptions, or embedded parameters
    Affected if Any dashboard contains malicious JavaScript code or suspicious URL parameters
  4. Audit access logs for crafted Analytics URLs
    Search web logs (typically in /var/log/gitlab/nginx) for requests to /-/analytics/dashboards containing patterns like `<script`, `javascript:`, `onerror=`, `onload=`, or other XSS vectors
    Affected if Logs show requests with XSS payloads directed at Analytics Dashboards endpoints

User is affected if running a vulnerable GitLab version (16.0.0-17.3.6, 17.4.0-17.4.3, or 17.5.0-17.5.1) AND Analytics Dashboards feature is enabled and accessible to users.

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.3.7 / 17.4.4 / 17.5.2 or later
Fixed in 17.3.717.4.417.5.2
Interim mitigation

Upgrade GitLab to version 17.3.7, 17.4.4, 17.5.2 or later. If immediate upgrading is not possible, restrict access to Analytics Dashboards features pending the patch.

Recommended fix High confidence

Upgrade to GitLab 17.3.7, 17.4.4, or 17.5.2 (or later) depending on your current major version line

  1. 1. Backup your GitLab instance database and repositories before upgrading
  2. 2. Determine your current GitLab version by running `gitlab-rake gitlab:env:info`
  3. 3. For GitLab 16.x installations: upgrade to version 17.3.7 or later
  4. 4. For GitLab 17.4.x installations: upgrade to version 17.4.4 or later
  5. 5. For GitLab 17.5.x installations: upgrade to version 17.5.2 or later
  6. 6. Follow the official GitLab upgrade documentation for your installation method (Omnibus, source, or Helm chart)
  7. 7. After upgrade, run `sudo gitlab-ctl reconfigure` if using Omnibus
  8. 8. Verify the upgrade was successful by checking the GitLab version and confirming the Analytics Dashboards functionality works correctly
Caveat Review GitLab release notes for breaking changes when upgrading between major versions (e.g., 16.x to 17.x); patch version upgrades within the same minor release typically have minimal breaking changes

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

Fix this in GitLab Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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