Sunday, February 9, 2025
HomeCVE/vulnerabilityGitLab Security Update - Patch for Multiple Vulnerabilities

GitLab Security Update – Patch for Multiple Vulnerabilities

Published on

SIEM as a Service

Follow Us on Google News

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
Divya is a Senior Journalist at GBhackers covering Cyber Attacks, Threats, Breaches, Vulnerabilities and other happenings in the cyber world.

Latest articles

UK Pressures Apple to Create Global Backdoor To Spy on Encrypted iCloud Access

United Kingdom has reportedly ordered Apple to create a backdoor allowing access to all...

Autonomous LLMs Reshaping Pen Testing: Real-World AD Breaches and the Future of Cybersecurity

Large Language Models (LLMs) are transforming penetration testing (pen testing), leveraging their advanced reasoning...

Securing GAI-Driven Semantic Communications: A Novel Defense Against Backdoor Attacks

Semantic communication systems, powered by Generative AI (GAI), are transforming the way information is...

Cybercriminals Target IIS Servers to Spread BadIIS Malware

A recent wave of cyberattacks has revealed the exploitation of Microsoft Internet Information Services...

Supply Chain Attack Prevention

Free Webinar - Supply Chain Attack Prevention

Recent attacks like Polyfill[.]io show how compromised third-party components become backdoors for hackers. PCI DSS 4.0’s Requirement 6.4.3 mandates stricter browser script controls, while Requirement 12.8 focuses on securing third-party providers.

Join Vivekanand Gopalan (VP of Products – Indusface) and Phani Deepak Akella (VP of Marketing – Indusface) as they break down these compliance requirements and share strategies to protect your applications from supply chain attacks.

Discussion points

Meeting PCI DSS 4.0 mandates.
Blocking malicious components and unauthorized JavaScript execution.
PIdentifying attack surfaces from third-party dependencies.
Preventing man-in-the-browser attacks with proactive monitoring.

More like this

UK Pressures Apple to Create Global Backdoor To Spy on Encrypted iCloud Access

United Kingdom has reportedly ordered Apple to create a backdoor allowing access to all...

Autonomous LLMs Reshaping Pen Testing: Real-World AD Breaches and the Future of Cybersecurity

Large Language Models (LLMs) are transforming penetration testing (pen testing), leveraging their advanced reasoning...

Securing GAI-Driven Semantic Communications: A Novel Defense Against Backdoor Attacks

Semantic communication systems, powered by Generative AI (GAI), are transforming the way information is...