HomeVulnerabilityImportant GitLab bug lets attackers run pipelines as any consumer

Important GitLab bug lets attackers run pipelines as any consumer

A vital vulnerability is affecting sure variations of GitLab Group and Enterprise Version merchandise, which might be exploited to run pipelines as any consumer.

GitLab is a well-liked web-based open-source software program undertaking administration and work monitoring platform. It has an estimated a million energetic license customers.

The security difficulty addressed within the lasted replace is tracked as CVE-2024-5655 and has a severity rating of 9.6 out of 10. Below sure circumstances, which the seller didn’t outline, an attacker might leverage it to set off a pipeline as one other consumer.

GitLab pipelines are a function of the Steady Integration/Steady Deployment (CI/CD) system that allows customers to robotically run processes and duties, both in parallel or in sequence, to construct, check, or deploy code modifications.

The vulnerability impacts all GitLab CE/EE variations from 15.8 by 16.11.4, 17.0.0 to 17.0.2, and 17.1.0 to 17.1.0.

“We strongly suggest that every one installations operating a model affected by the problems described under are upgraded to the most recent model as quickly as attainable” – GitLab

GitLab has addressed the vulnerability by releasing variations 17.1.1, 17.0.3, and 16.11.5, and recommends customers to use the updates as quickly as attainable.

See also  How a digital design agency navigated its SOC 2 audit

The seller additionally informs that upgrading to the most recent variations comes with two breaking modifications that customers ought to concentrate on:

  1. Pipelines will not run robotically when a merge request is re-targeted after its earlier goal department is merged. Customers should manually begin the pipeline to execute CI for his or her modifications.
  2. CI_JOB_TOKEN is now disabled by default for GraphQL authentication ranging from model 17.0.0, with this modification backported to variations 17.0.3 and 16.11.5. To entry the GraphQL API, customers have to configure one of many supported token varieties for authentication.

The newest GitLab replace additionally introduces security fixes for 13 different points, the severity of three of them being rated as “excessive” (CVSS v3.1 rating: 7.5 – 8.7). These three are summarized as follows:

  • CVE-2024-4901: Saved XSS vulnerability permitting malicious commit notes from imported initiatives to inject scripts, doubtlessly resulting in unauthorized actions and information publicity.
  • CVE-2024-4994: A CSRF vulnerability within the GraphQL API permitting attackers to execute arbitrary GraphQL mutations by tricking authenticated customers into making undesirable requests, doubtlessly resulting in information manipulation and unauthorized operations.
  • CVE-2024-6323: Authorization flaw in GitLab’s world search function permitting attackers to view search outcomes from non-public repositories inside public initiatives, doubtlessly resulting in data leaks and unauthorized entry to delicate information.
See also  Home windows Downgrade Attack Dangers Exposing Patched Programs to Outdated Vulnerabilities

Sources for GitLab updates can be found right here, whereas GitLab Runner pointers might be discovered on this web page.

- Advertisment -spot_img
RELATED ARTICLES

LEAVE A REPLY

Please enter your comment!
Please enter your name here

- Advertisment -

Most Popular