dbcve.org
GitLabApplication

CVE-2024-1066

MEDIUM · 6.5 CVSS v3.1 Published 2024-02-07
Fix available
A fix is available. Upgrade to 16.6.7 / 16.7.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 EE affecting all versions from 13.3.0 prior to 16.6.7, 16.7 prior to 16.7.5, and 16.8 prior to 16.8.2 which allows an attacker to do a resource exhaustion using GraphQL `vulnerabilitiesCountByDay`

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

A resource exhaustion vulnerability in GitLab EE's GraphQL API endpoint 'vulnerabilitiesCountByDay' allows authenticated attackers to overwhelm server resources by exploiting insufficient input validation or query limits on this endpoint, causing denial of service.

MitigationUpgrade GitLab EE to version 16.6.7, 16.7.5, 16.8.2 or later. As a compensating control, implement rate limiting on GraphQL endpoints at the load balancer or reverse proxy level.

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:>= 13.3.0, < 16.6.7>= 16.7.0, < 16.7.5>= 16.8.0, < 16.8.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. Identify GitLab edition
    Run `grep -E '^git_type|edition' /opt/gitlab/version-manifest.txt` or check the admin panel under Admin Area > Overview > License to confirm if running Enterprise Edition (EE). The vulnerability affects only GitLab EE, not CE.
    Affected if Running GitLab CE (Community Edition) means not affected by this CVE.
  2. Check installed GitLab version
    Run `gitlab-rake gitlab:env:info` or `cat /opt/gitlab/version` to obtain the exact version number. Compare against affected ranges: 13.3.0 to 16.6.6, 16.7.0 to 16.7.4, or 16.8.0 to 16.8.1.
    Affected if Installed version falls within any of these ranges: >=13.3.0 and <16.6.7, OR >=16.7.0 and <16.7.5, OR >=16.8.0 and <16.8.2.
  3. Verify GraphQL API is accessible
    Check if the GraphQL endpoint responds by sending a GET request to `https://<your-gitlab-host>/api/graphql` or reviewing web server configuration for GraphQL route exposure.
    Affected if The GraphQL API endpoint is exposed and reachable from the network.
  4. Confirm authenticated API access is possible
    Review user authentication settings under Admin Area > Settings > General > Visibility and access controls. Verify that the API allows authenticated user access rather than being restricted to admin-only.
    Affected if Authenticated (non-admin) users can access the GitLab API, allowing them to reach the vulnerable endpoint.
  5. Check for rate limiting on GraphQL endpoints
    Inspect the load balancer, reverse proxy (nginx/apache), or GitLab configuration under `/etc/gitlab/gitlab.rb` for rate limiting rules on the `/api/graphql` path.
    Affected if No rate limiting or query depth limits are configured on the GraphQL endpoint.

Environment is affected if running GitLab EE in an affected version range with the GraphQL API accessible to authenticated users without rate limiting in place.

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.6.7 / 16.7.5 / 16.8.2 or later
Fixed in 16.6.716.7.516.8.2
Interim mitigation

Upgrade GitLab EE to version 16.6.7, 16.7.5, 16.8.2 or later. As a compensating control, implement rate limiting on GraphQL endpoints at the load balancer or reverse proxy level.

Recommended fix High confidence

16.6.7, 16.7.5, or 16.8.2 (or any later stable release such as 16.9.x, 16.10.x, etc.)

  1. Review the GitLab upgrade documentation for your installation method (Omnibus, source, or Helm chart)
  2. Ensure you have a complete backup of your GitLab instance and database
  3. Plan for maintenance window as upgrade will require service restart
  4. For Omnibus installations: run 'apt-get update && apt-get install gitlab-ee' (Debian/Ubuntu) or 'yum update gitlab-ee' (RHEL/CentOS)
  5. For source installations: follow the GitLab upgrade guide to compile the specific version
  6. After upgrade, verify the GitLab version matches the expected fixed release using 'gitlab-rake gitlab:version'
  7. Test GraphQL API functionality to confirm the fix is applied
  8. Monitor system resources to verify resource exhaustion is no longer possible via vulnerabilitiesCountByDay endpoint
Caveat Standard GitLab minor version upgrade considerations apply; review release notes for any breaking changes between your current and target 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
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
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,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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