Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2024-10240 Overview
CVE-2024-10240 is an information disclosure vulnerability in GitLab Enterprise Edition (EE) that allows unauthenticated users to read limited information about merge requests (MRs) in private projects. The flaw affects GitLab EE versions 17.3 through 17.3.6, 17.4 through 17.4.3, and 17.5 through 17.5.1. GitLab addressed the issue in patch releases 17.3.7, 17.4.4, and 17.5.2 on November 13, 2024. The weakness is tracked under CWE-497: Exposure of Sensitive System Information to an Unauthorized Control Sphere.
Critical Impact
Unauthenticated attackers can retrieve merge request metadata from private GitLab projects through an exposed API endpoint, breaking project confidentiality boundaries.
Affected Products
- GitLab EE 17.3 through 17.3.6
- GitLab EE 17.4 through 17.4.3
- GitLab EE 17.5 through 17.5.1
Discovery Timeline
- 2024-11-13 - GitLab releases patch versions 17.3.7, 17.4.4, and 17.5.2
- 2024-11-26 - CVE-2024-10240 published to NVD
- 2026-06-17 - Last updated in NVD database
Technical Details for CVE-2024-10240
Vulnerability Analysis
The vulnerability resides in a GitLab API endpoint that fails to enforce proper authorization checks before returning merge request information. Under specific conditions, the endpoint responds to unauthenticated requests with data about merge requests that belong to private projects. The attack requires only network access to the GitLab instance and no user interaction or privileges. Confidentiality is affected, while integrity and availability remain intact. See the GitLab patch release notes for the vendor's description.
Root Cause
The root cause is missing or incomplete authorization enforcement in an API handler responsible for returning merge request details. The handler surfaces information that should be gated by project visibility and user permission checks. Because the endpoint evaluates request parameters without validating the caller's access to the parent project, metadata about MRs in private projects can be returned to anonymous callers under certain conditions. This maps to [CWE-497] exposure of information intended to be restricted.
Attack Vector
Exploitation is network-based and requires no authentication. An attacker queries the vulnerable API endpoint and parses the response for MR metadata belonging to private projects. The data surface is limited, which is reflected in the low confidentiality impact and medium rating. No proof-of-concept is publicly indexed, and the issue is not listed in the CISA Known Exploited Vulnerabilities catalog. Technical discussion is available in the GitLab issue tracker entry #493188.
Detection Methods for CVE-2024-10240
Indicators of Compromise
- Unauthenticated HTTP requests to GitLab merge request API endpoints returning 200 OK responses.
- Anomalous access patterns from external IP addresses enumerating project or MR identifiers.
- Access log entries lacking associated session tokens or PRIVATE-TOKEN headers that still return MR data payloads.
Detection Strategies
- Review GitLab production_json.log and api_json.log for API calls to merge request endpoints without an authenticated user_id.
- Correlate web server access logs for high-volume enumeration of sequential MR or project IDs from a single source.
- Alert on API responses containing MR metadata when the request originates without authentication headers.
Monitoring Recommendations
- Forward GitLab application and reverse-proxy logs to a centralized analytics platform for authorization anomaly detection.
- Baseline normal unauthenticated API traffic volumes and alert on deviations.
- Monitor patch compliance across GitLab instances to confirm all nodes run 17.3.7, 17.4.4, 17.5.2, or later.
How to Mitigate CVE-2024-10240
Immediate Actions Required
- Upgrade GitLab EE to 17.3.7, 17.4.4, 17.5.2, or a later release as published in the GitLab patch advisory.
- Audit API access logs for signs of pre-patch unauthenticated access to private project MR endpoints.
- Rotate any sensitive data referenced in MR titles, descriptions, or branch names of private projects if exposure is suspected.
Patch Information
GitLab fixed the issue in versions 17.3.7, 17.4.4, and 17.5.2, released on November 13, 2024. The vendor advisory documents the fix as "Information disclosure through an API endpoint." Both Community Edition and Enterprise Edition should be updated, even though the advisory describes the issue in EE context. Refer to the official GitLab release post for upgrade instructions.
Workarounds
- No vendor-supplied workaround exists; applying the patched version is the only supported remediation.
- Restrict network exposure of the GitLab API to trusted ranges where feasible using firewall or reverse-proxy rules until patching completes.
- Place a web application firewall (WAF) rule in front of merge request API routes to require authentication headers for all requests during the patch window.
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

