CVE-2024-4612

criticalcovered by 1 sourcefirst seen 2024-09-11

On September 11, 2024, we released versions 17.3.2, 17.2.5, 17.1.7 for GitLab Community Edition (CE) and Enterprise Edition (EE). These versions contain important bug and security fixes, and we strongly recommend that all self-managed GitLab installations be upgraded to one of these versions immediately. GitLab.com is already running the patched version. GitLab Dedicated customers do not need to take action. GitLab releases fixes for vulnerabilities in 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 committed 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 Execute environment stop actions as the owner of the stop action job Critical Prevent code injection in Product Analytics funnels YAML High SSRF via Dependency Proxy High Denial of Service via sending a a specific POST request High CI_JOB_TOKEN can be used to obtain GitLab session t

CSIRTS triage

What: Multiple important bug and security fixes have been released.
Who is affected: All self-managed GitLab installations are affected.
Urgency: Remediation is critical due to the high 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-4612

Get an email if CVE-2024-4612 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.36% 30-day exploitation probability — currently an unlikely target, but scores change as exploit code circulates. Riskier than 29% of all EPSS-scored CVEs.

Advisory coverage (1)

criticalGitLab Critical Patch Release: 17.3.2, 17.2.5, 17.1.7gitlab · 2024-09-11

External references

NVD record for CVE-2024-4612

CVE.org record

Embed the live status

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

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