CVE-2024-3127

criticalcovered by 1 sourcefirst seen 2024-08-21

On August 21, 2024, we released versions 17.3.1, 17.2.4, 17.1.6 for GitLab Community Edition (CE) and Enterprise Edition (EE). These versions contain important bug and security fixes, and we strongly recommend that all GitLab installations be upgraded to one of these versions immediately. GitLab.com is already running the patched version. GitLab releases fixes for vulnerabilities in dedicated patch releases. There are two types of patch releases: scheduled releases, and ad-hoc critical patches for high-severity vulnerabilities. Scheduled releases are released twice a month on the second and fourth Wednesdays. For more information, you can visit our releases handbook and security FAQ . You can see all of GitLab release blog posts here . For security fixes, the issues detailing each vulnerability are made public on our issue tracker 30 days after the release in which they were patched. We are dedicated to ensuring all aspects of GitLab that are exposed to customers or that host customer data are held to the highest security standards. As part of maintaining good security hygiene, it is highly recommended that all customers upgrade to the latest patch release for their supported version. You can read more best practices in securing your GitLab instance in our blog post. Recommended Action We strongly recommend that all installations running a version affected by the issues described below are upgraded to the latest version as soon as possible . When no specific deployment type (omnibus, source code, helm chart, etc.) of a product is mentioned, this means all types are affected. Security fixes Table of security fixes Title Severity The GitLab Web Interface Does Not Guarantee Information Integrity When Downloading Source Code from Releases. Medium Denial of Service by importing maliciously crafted GitHub repository Medium Prompt injection in “Resolve Vulnerabilty” results in arbitrary command execution in victim’s pipeline Medium An unauthorized user can perform certain

CSIRTS triage

What: The release contains important bug and security fixes.
Who is affected: All GitLab installations using versions prior to 17.3.1, 17.2.4, or 17.1.6.
Urgency: Remediation is urgent due to the critical severity of the vulnerabilities.
Action: Upgrade to one of the patched versions immediately.

AI-assisted analysis generated from the source advisory — verify against the original.

⚡ Watch CVE-2024-3127

Get an email if CVE-2024-3127 is added to CISA KEV, gains public exploit code, or a new advisory cites it — max one per day, one-click unsubscribe.

Exploitation outlook

Low exploitation risk0.33% 30-day exploitation probability — currently an unlikely target, but scores change as exploit code circulates. Riskier than 24% of all EPSS-scored CVEs.

Advisory coverage (1)

criticalGitLab Patch Release: 17.3.1, 17.2.4, 17.1.6gitlab · 2024-08-21

External references

NVD record for CVE-2024-3127

CVE.org record

Embed the live status

— this badge updates automatically when the KEV or exploit status changes. How to embed it →

[![CVE-2024-3127 status](https://www.csirts.com/badge/CVE-2024-3127)](https://www.csirts.com/cve/CVE-2024-3127)