dbcve.org
GitLabApplication

CVE-2024-13054

MEDIUM · 6.5 CVSS v3.1 Published 2025-03-13
Fix available
A fix is available. Upgrade to 17.7.7 / 17.8.5 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 was discovered in GitLab CE/EE affecting all versions before 17.7.7, 17.8 prior to 17.8.5, and 17.9 prior to 17.9.2. where a denial of service vulnerability could allow an attacker to cause a system reboot under certain conditions.

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

A denial of service vulnerability in GitLab CE/EE allows attackers to cause system reboot under certain conditions across unpatched versions prior to 17.7.7, 17.8.5, and 17.9.2.

MitigationUpgrade GitLab to version 17.7.7, 17.8.5, 17.9.2 or later to patch this vulnerability.

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:< 17.7.7>= 17.8.0, < 17.8.5>= 17.9.0, < 17.9.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. Check installed GitLab version
    Run `sudo gitlab-rake gitlab:env:info` or check the GitLab admin interface under Help > Version, or examine /opt/gitlab/version-manifest.txt
    Affected if Version is < 17.7.7, OR >= 17.8.0 and < 17.8.5, OR >= 17.9.0 and < 17.9.2
  2. Confirm exact version number
    Run `cat /opt/gitlab/embedded/service/gitlab-rails/VERSION` to get the precise installed version
    Affected if The exact version falls into any of the three vulnerable ranges
  3. Compare against fixed releases
    Verify the version is not 17.7.7 or later, not 17.8.5 or later, and not 17.9.2 or later
    Affected if The version is lower than any of these fixed release numbers

The environment is affected if the installed GitLab version is less than 17.7.7, or between 17.8.0 and 17.8.4 inclusive, or between 17.9.0 and 17.9.1 inclusive.

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.7.7 / 17.8.5 / 17.9.2 or later
Fixed in 17.7.717.8.517.9.2
Interim mitigation

Upgrade GitLab to version 17.7.7, 17.8.5, 17.9.2 or later to patch this vulnerability.

Recommended fix High confidence

17.9.2 (or latest 17.x stable release)

  1. Review the GitLab upgrade documentation at https://docs.gitlab.com/ee/update/ for your specific installation method (Omnibus, source, etc.)
  2. Take a complete backup of your GitLab instance including database and repositories before proceeding
  3. Identify your current GitLab version using the GitLab Rails console: `gitlab-rake gitlab:env:info` or the admin area UI
  4. Plan your upgrade path based on your current version - for versions before 17.7, upgrade to 17.7.7 first; for 17.8.x, upgrade to 17.8.5; for 17.9.0-17.9.1, upgrade to 17.9.2
  5. For Omnibus installations: stop GitLab services with `gitlab-ctl stop`, then run the package manager upgrade command for your OS (e.g., `apt-get update && apt-get install gitlab-ce` or `yum install gitlab-ce`)
  6. For source installations: follow the upgrade guide to clone the specific tagged version and run database migrations
  7. After upgrade, verify GitLab is running: `gitlab-rake gitlab:check`
  8. Confirm the vulnerability is patched by checking the version: `gitlab-rake gitlab:env:info` should show version 17.7.7, 17.8.5, or 17.9.2 or later
Caveat Standard GitLab upgrade precautions apply - review release notes for any between-version breaking changes and ensure database backup before migrating

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