Cyber Security News

GitLab Security Update – Patch for Multiple Vulnerabilities

GitLab, the widely adopted DevOps platform, has announced the immediate release of versions 17.8.1, 17.7.3, and 17.6.4 for both its Community Edition (CE) and Enterprise Edition (EE).

These updates address multiple security vulnerabilities and provide critical fixes, underscoring GitLab’s commitment to maintaining the highest security standards.

The vulnerabilities addressed in these updates include a high-severity Stored XSS via Asciidoctor render, a medium-severity issue where a developer could exfiltrate protected CI/CD variables via CI lint, and another medium-severity vulnerability involving cyclic references of epics leading to resource exhaustion.

GitLab strongly encourages self-managed users to upgrade to the latest versions immediately to safeguard their systems.

Are you from SOC/DFIR Teams? - Analyse Malware Files & Links with ANY.RUN Sandox -> Try for Free

Vulnerability Breakdown

1. Stored XSS via Asciidoctor Render – CVE-2025-0314

  • CVE-2025-0314 – Improper rendering of specific file types allowed for a cross-site scripting (XSS) attack. This issue affects all versions from 17.2 before 17.6.4, 17.7 before 17.7.3, and 17.8 before 17.8.1.

2. Developer Could Exfiltrate Protected CI/CD Variables via CI Lint – CVE-2024-11931

  • CVE-2024-11931 – Developers with specific roles could potentially exploit CI lint to access protected CI/CD variables. This issue affects versions starting from 17.0 before 17.6.4, 17.7 before 17.7.3, and 17.8 before 17.8.1.

3. Cyclic Reference of Epics Leads to Resource Exhaustion – CVE-2024-6324

  • CVE-2024-6324 – Creating cyclic references between epics could result in denial-of-service (DoS) attacks. This issue impacts versions starting from 15.7 before 17.6.4, 17.7 before 17.7.3, and 17.8 before 17.8.1.

GitLab has already deployed these updates on GitLab.com, meaning users on the hosted platform are automatically protected. GitLab Dedicated customers do not need to take action. However, self-managed GitLab users are urged to:

  1. Upgrade to one of the patched versions (17.8.1, 17.7.3, or 17.6.4) immediately.
  2. Follow best practices for securing GitLab instances, which are outlined in GitLab’s official blog.

GitLab remains steadfast in prioritizing security by addressing vulnerabilities through timely patches.

Security issues are made public 30 days after patch releases to ensure transparency while protecting vulnerabilities during the critical update window.

Integrating Application Security into Your CI/CD Workflows Using Jenkins & Jira -> Free Webinar

Divya

Divya is a Senior Journalist at GBhackers covering Cyber Attacks, Threats, Breaches, Vulnerabilities and other happenings in the cyber world.

Recent Posts

Cisco Unified Intelligence Center Vulnerability Allows Privilege Escalation

Cisco has disclosed two security vulnerabilities in its Unified Intelligence Center that could allow authenticated…

12 minutes ago

New NIST Security Metric Aims to Pinpoint Exploited Vulnerabilities

Researchers from the National Institute of Standards and Technology (NIST) and the Cybersecurity and Infrastructure…

1 hour ago

Versa Concerto 0-Day Flaw Enables Remote Code Execution by Bypassing Authentication

Security researchers have uncovered multiple critical vulnerabilities in Versa Concerto, a widely deployed network security…

5 hours ago

Hackers Targets Coinbase Users Targeted in Advanced Social Engineering Hack

Coinbase users have become the prime targets of an intricate social engineering campaign since early…

6 hours ago

Hackers Exploit PyBitmessage Library to Evade Antivirus and Network Security Detection

The AhnLab Security Intelligence Center (ASEC) has uncovered a new strain of backdoor malware being…

6 hours ago

Several GitLab Vulnerabilities Enable Attackers to Launch DoS Attacks

GitLab has issued critical security patches addressing 11 vulnerabilities across its Community Edition (CE) and…

6 hours ago