dbcve.org
GitLabApplication

CVE-2024-8177

HIGH · 7.5 CVSS v3.1 Published 2024-11-26
Fix available
A fix is available. Upgrade to 17.4.5 / 17.5.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 was discovered in GitLab CE/EE affecting all versions starting from 15.6 prior to 17.4.5, starting from 17.5 prior to 17.5.3, starting from 17.6 prior to 17.6.1 which could cause Denial of Service via integrating a malicious harbor registry.

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 · moderate confidence

GitLab CE/EE contains a denial of service vulnerability in its Harbor registry integration functionality. When GitLab attempts to integrate with a malicious or compromised Harbor registry, the registry can cause GitLab to become unresponsive or crash, likely through malformed responses that trigger resource exhaustion or processing loops.

MitigationUpgrade GitLab to versions 17.4.5, 17.5.3, 17.6.1 or later. Until upgraded, avoid integrating with untrusted or third-party Harbor registries.

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.6.0, < 17.4.5>= 17.5.0, < 17.5.3= 17.6.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. Check installed GitLab version
    Run `gitlab-rake gitlab:env:info` or check /opt/gitlab/version to get the exact GitLab version number
    Affected if Version is 15.6.0 to 17.4.4, 17.5.0 to 17.5.2, or exactly 17.6.0
  2. Verify Harbor registry integration is configured
    Check GitLab admin settings at Admin Area > Settings > Registry or review /etc/gitlab/gitlab.rb for `gitlab_rails['registry_enabled']` and Harbor-related settings
    Affected if Harbor registry is enabled or any Harbor endpoints are configured as container registries
  3. Identify configured registry endpoints
    Query the database: `sudo gitlab-psql -d gitlabhq_production -c "SELECT name, url FROM registry_repositories WHERE url LIKE '%harbor%';"` or check project/container registry settings
    Affected if Any container registries point to Harbor servers, particularly untrusted or third-party Harbor instances

You are affected if your GitLab version falls within the vulnerable ranges AND you have Harbor registry integration enabled with a configured Harbor endpoint.

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.4.5 / 17.5.3 or later
Fixed in 17.4.517.5.3
Interim mitigation

Upgrade GitLab to versions 17.4.5, 17.5.3, 17.6.1 or later. Until upgraded, avoid integrating with untrusted or third-party Harbor registries.

Recommended fix High confidence

17.4.5, 17.5.3, or 17.6.1 (depending on your current major.minor version)

  1. Identify your current GitLab version by running `sudo gitlab-rake gitlab:env:info` or checking the GitLab admin area
  2. Determine which upgrade path applies based on your current version (17.4.x, 17.5.x, or 17.6.0)
  3. For GitLab installations using Omnibus: Run `sudo gitlab-ctl stop` to stop services, then `sudo apt-get update && sudo apt-get install gitlab-ce` (or gitlab-ee) to upgrade to the fixed version
  4. For installations from source: Navigate to your GitLab installation directory, run `git fetch --all && git checkout VERSION` where VERSION is the fixed release tag (e.g., v17.4.5, v17.5.3, or v17.6.1), then run bundle install --deployment and compile assets
  5. After upgrade, run `sudo gitlab-ctl reconfigure` to apply configuration changes
  6. Verify the upgrade was successful by running `sudo gitlab-rake gitlab:check`
Caveat Minor upgrades typically have low risk but always review the GitLab release notes for any special migration steps or deprecation warnings specific to your version

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
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
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,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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