CVE-2024-1066: Resource exhaustion using GraphQL vulnerabilitiesCountByDay

Published Feb 7, 2024
·
Updated

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

Other sources

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. This is a medium severity issue (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H, 6.5). It is now mitigated in the latest release and is assigned CVE-2024-1066.

GitLab

Affected Software

4 affected componentsFixes available
GitLab GitLab>=13.3.0<16.6.7
GitLab GitLab>=16.7.0<16.7.5
GitLab GitLab>=16.8.0<16.8.2
GitLab GitLab EE>=13.3.0<16.6.7, >=16.7<16.7.5, >=16.8<16.8.2
16.6.716.7.516.8.2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 16.6.7Fixed in 16.7.5Fixed in 16.8.2
  2. Upgrade

    Upgrade GitLab EE to a version that resolves this vulnerability.

    Fixed in 16.6.7
  3. Upgrade

    Upgrade GitLab EE to a version that resolves this vulnerability.

    Fixed in 16.7.5
  4. Upgrade

    Upgrade GitLab EE to a version that resolves this vulnerability.

    Fixed in 16.8.2
  5. Compensating control

    If you cannot upgrade immediately, mitigate the resource exhaustion risk caused by GraphQL vulnerabilitiesCountByDay by limiting access/rate to the affected GraphQL functionality until patched (issue is mitigated in the latest release and assigned CVE-2024-1066).

Event History

Feb 7, 2024
CVE Published
via MITRE·10:02 PM
Data Sourced
via MITRE·10:02 PM
RemedyDescriptionSeverityWeakness
Data Sourced
via NVD·10:15 PM
DescriptionSeverityWeaknessAffected Software
Apr 22, 2026
Data Sourced
via GitLab·08:52 AM
DescriptionSeverityAffected Software

Peer vulnerabilities

Found alongside the following vulnerabilities.

Frequently Asked Questions

1

What is the severity of CVE-2024-1066?

CVE-2024-1066 is considered a high severity vulnerability due to its potential for resource exhaustion in GitLab.

2

How do I fix CVE-2024-1066?

To fix CVE-2024-1066, upgrade your GitLab instance to versions 16.6.7, 16.7.5, or 16.8.2 or later.

3

What versions of GitLab are vulnerable to CVE-2024-1066?

All GitLab versions from 13.3.0 prior to 16.6.7, and from 16.7 prior to 16.7.5 and 16.8 prior to 16.8.2 are vulnerable to CVE-2024-1066.

4

What type of attack does CVE-2024-1066 allow?

CVE-2024-1066 allows an attacker to perform a resource exhaustion attack using the GraphQL `vulnerabilitiesCountByDay` query.

5

Is CVE-2024-1066 related to GitLab's GraphQL interface?

Yes, CVE-2024-1066 specifically affects GitLab's GraphQL interface, allowing for potential misuse.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203