dbcve.org
GitLabApplication

CVE-2024-8977

HIGH · 8.1 CVSS v3.1 Published 2024-10-10
Fix available
A fix is available. Upgrade to 17.2.9 / 17.3.5 or later.
See remediation →
87/100
Remediation priority · High
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 EE affecting all versions starting from 15.10 prior to 17.2.9, from 17.3 prior to 17.3.5, and from 17.4 prior to 17.4.2. Instances with Product Analytics Dashboard configured and enabled could be vulnerable to SSRF attacks.

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

Server-Side Request Forgery (SSRF) vulnerability in GitLab EE allows attackers to make the server perform unintended requests to internal or external resources. The flaw exists in the Product Analytics Dashboard feature when configured and enabled, potentially exposing internal services and infrastructure.

MitigationUpgrade GitLab to version 17.2.9, 17.3.5, or 17.4.2 or later. Until patching is feasible, consider disabling the Product Analytics Dashboard feature as a temporary workaround.

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:>= 15.10, < 17.2.9>= 17.3.0, < 17.3.5>= 17.4.0, < 17.4.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
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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. Check installed GitLab version
    Run `sudo gitlab-rake gitlab:version` or check the GitLab admin panel under Help > Version to determine the exact version running in your environment.
    Affected if The version falls within any of these ranges: 15.10 to 17.2.8, 17.3.0 to 17.3.4, or 17.4.0 to 17.4.1. If your version is outside these ranges, you are not affected by this CVE.
  2. Verify Product Analytics feature status
    Navigate to GitLab Admin Area > Analytics > Product Analytics, or check the gitlab.yml configuration file for product_analytics settings. Look for whether the feature is enabled or disabled.
    Affected if Product Analytics is enabled and configured. If the feature is disabled entirely, the attack surface does not exist regardless of version.
  3. Check Product Analytics collector configuration
    Inspect the Product Analytics collector settings in the GitLab admin interface or configuration. Verify if a collector endpoint is configured and pointing to a valid destination.
    Affected if A collector is configured and active. The SSRF vulnerability specifically targets the Product Analytics Dashboard feature when it has collector settings configured.
  4. Confirm analytics Dashboards module access
    Review which projects or groups have access to the Product Analytics Dashboard. Check if any projects have Product Analytics dashboards created or enabled.
    Affected if Product Analytics Dashboards are accessible to users. The vulnerability is exploitable when dashboards can be accessed and the feature is enabled.

You are affected if your GitLab version is within 15.10-17.2.8, 17.3.0-17.3.4, or 17.4.0-17.4.1 AND the Product Analytics Dashboard feature is enabled and 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 17.2.9 / 17.3.5 / 17.4.2 or later
Fixed in 17.2.917.3.517.4.2
Interim mitigation

Upgrade GitLab to version 17.2.9, 17.3.5, or 17.4.2 or later. Until patching is feasible, consider disabling the Product Analytics Dashboard feature as a temporary workaround.

Recommended fix High confidence

17.4.2 or later (recommended: latest stable 17.x release)

  1. 1. Back up your GitLab instance data and configuration 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 15.10 through 17.2.x: upgrade to version 17.2.9 or later.
  4. 4. For GitLab versions 17.3.0 through 17.3.x: upgrade to version 17.3.5 or later.
  5. 5. For GitLab versions 17.4.0 through 17.4.x: upgrade to version 17.4.2 or later.
  6. 6. Alternatively, upgrade directly to the latest stable release (17.5.0 or later) which contains all security fixes.
  7. 7. After upgrade, verify the Product Analytics Dashboard functionality and ensure GitLab is operational.
  8. 8. Review the GitLab upgrade documentation for your specific installation method (Omnibus, source, Helm chart) for detailed upgrade procedures.
Caveat Major version upgrades may introduce breaking changes; review GitLab release notes before upgrading across major versions

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