dbcve.org
GitLabApplication

CVE-2024-2454

MEDIUM · 6.5 CVSS v3.1 Published 2024-05-14
Fix available
A fix is available. Upgrade to 16.9.7 / 16.10.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 has been discovered in GitLab CE/EE affecting all versions starting from 15.11 prior to 16.9.7, starting from 16.10 prior to 16.10.5, and starting from 16.11 prior to 16.11.2. The pins endpoint is susceptible to DoS through a crafted request.

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 exists in GitLab CE/EE where the pins endpoint fails to properly handle crafted requests, allowing attackers to crash the service. This affects all versions from 15.11 through 16.11.1 across the specified release branches.

MitigationUpgrade GitLab to version 16.9.7, 16.10.5, or 16.11.2 or later. Until patched, monitor for abnormal request patterns to the pins endpoint.

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.11.0, < 16.9.7>= 16.10.0, < 16.10.5>= 16.11.0, < 16.11.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
    Access GitLab Admin area > Help > Version number, or run 'gitlab-rake gitlab:env:info' on the server, or check /opt/gitlab/version on the server
    Affected if Version falls within >= 15.11.0 and < 16.9.7, OR >= 16.10.0 and < 16.10.5, OR >= 16.11.0 and < 16.11.2
  2. Verify pins endpoint exists
    Attempt a GET request to /api/v4/pins or check GitLab routes for pins-related API endpoints using 'gitlab-rake routes | grep pin'
    Affected if The pins endpoint is accessible and responds to requests
  3. Check for service instability
    Review GitLab logs (/var/log/gitlab/gitlab-rails/production.log) for crashes or errors around the time of requests to the pins endpoint, or check 'gitlab-ctl status' for unexpected service restarts
    Affected if Service crashes or abnormal restarts coincide with pins endpoint access
  4. Identify abnormal request patterns
    Analyze web server or load balancer logs for repeated or crafted requests to pins-related endpoints, looking for request spikes or unusual patterns
    Affected if Large volume of requests to pins endpoint is observed from single or multiple sources

A user is affected if their GitLab version falls within the affected ranges AND the pins endpoint is accessible, potentially evidenced by service crashes after pins endpoint requests.

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.9.7 / 16.10.5 / 16.11.2 or later
Fixed in 16.9.716.10.516.11.2
Interim mitigation

Upgrade GitLab to version 16.9.7, 16.10.5, or 16.11.2 or later. Until patched, monitor for abnormal request patterns to the pins endpoint.

Recommended fix High confidence

16.11.2 (or 16.10.5 for 16.10.x branches, or 16.9.7 for 15.11.x/16.9.x branches)

  1. Backup your GitLab instance data and configuration before proceeding with the upgrade
  2. Verify your current GitLab version by navigating to the GitLab Admin Area or running `gitlab-rake gitlab:env:info`
  3. Plan your upgrade path based on your current version: if on 15.11.x upgrade to 16.9.7; if on 16.10.x upgrade to 16.10.5; if on 16.11.x upgrade to 16.11.2
  4. For self-managed installations, follow the standard GitLab upgrade procedure for your installation method (Omnibus, source, or Docker)
  5. After upgrade, verify the new version is running with `gitlab-rake gitlab:env:info`
  6. Test that the pins endpoint is accessible and functioning normally
Caveat Review GitLab 16.11 release notes for any breaking changes specific to your installation type before upgrading

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
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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