GitLab warns of critical pipeline execution vulnerability

GitLab warns of critical pipeline execution vulnerability

September 12, 2024 at 10:50AM

GitLab has released critical updates to address multiple vulnerabilities, including the most severe CVE-2024-6678, allowing an attacker to trigger pipelines as arbitrary users. The release encompasses versions 17.3.2, 17.2.5, and 17.1.7 for both CE and EE, and addresses a total of 18 security issues. GitLab urges immediate upgrading to the latest version.

From the meeting notes, I have gathered the following key takeaways:

– GitLab has released critical updates to address multiple vulnerabilities, including the most severe one (CVE-2024-6678), which allows an attacker to trigger pipelines as arbitrary users under certain conditions.

– The release covers versions 17.3.2, 17.2.5, and 17.1.7 for both GitLab Community Edition (CE) and Enterprise Edition (EE), and patches a total of 18 security issues as part of the bi-monthly scheduled security updates.

– It is important to note that the CVE-2024-6678 vulnerability has a critical severity score of 9.9 and could enable an attacker to execute environment stop actions as the owner of the stop action job.

– GitLab recommends that all installations running a version affected by the disclosed issues be promptly upgraded to the latest version.

– GitLab pipelines are automated workflows used to build, test, and deploy code and are part of GitLab’s CI/CD system. They are designed to streamline the software development process by automating repetitive tasks and ensuring consistent testing and deployment of code changes.

– GitLab has also addressed arbitrary pipeline execution vulnerabilities in recent months, with fixes released in July 2024 (CVE-2024-6385), June 2024 (CVE-2024-5655), and September 2023 (CVE-2023-5009), all rated critical.

– The bulletin also lists four high-severity issues (CVE-2024-8640, CVE-2024-8635, CVE-2024-8124, and CVE-2024-8641) with scores between 6.7 and 8.5, each potentially allowing attackers to disrupt services, execute unauthorized commands, or compromise sensitive resources.

– For update instructions, source code, and packages, employees are directed to check out GitLab’s official download portal. The latest GitLab Runner packages are available there as well.

These are the key takeaways from the meeting notes provided. If you need further clarification or additional information, feel free to ask.

Full Article