There is a current IT security warning for GitLab. You can find out what vulnerabilities are involved, which products are affected and what you can do here.
The Federal Office for Security in Information Technology (BSI) reported a security advisory for GitLab on April 24, 2024. The report lists several vulnerabilities that can be exploited by attackers. The security vulnerability affects the UNIX operating system and the open source GitLab product.
The latest manufacturer recommendations regarding updates, workarounds and security patches for this vulnerability can be found here: GitLab Patch Release (Stand: 24.04.2024).
Multiple vulnerabilities reported for GitLab – Risk: high
Risk level: 3 (high)
CVSS Base Score: 8,5
CVSS Temporal Score: 7,4
Remoteangriff: Ja
The Common Vulnerability Scoring System (CVSS) is used to assess the severity of vulnerabilities in computer systems. The CVSS standard makes it possible to compare potential or actual security vulnerabilities based on various metrics in order to better prioritize countermeasures. The attributes “none”, “low”, “medium”, “high” and “critical” are used to determine the severity levels of a vulnerability. The Base Score evaluates the requirements for an attack (including authentication, complexity, privileges, user interaction) and its consequences. The temporal score also takes changes over time in the danger situation into account. According to the CVSS, the threat of the current vulnerability is classified as “high” with a base score of 8.5.
GitLab Bug: Vulnerabilities and CVE numbers
GitLab is a web application for version management for software projects based on git.
A remote, authenticated attacker could exploit multiple vulnerabilities in GitLab to bypass security measures to create a denial of service condition
The vulnerabilities were classified by individual serial numbers using the CVE (Common Vulnerabilities and Exposures) referencing system CVE-2024-1347, CVE-2024-4024, CVE-2024-2434, CVE-2024-2829 und CVE-2024-4006.
Systems affected by the GitLab security vulnerability at a glance
operating system
UNIX
Products
Open Source GitLab Open Source GitLab Open Source GitLab
General measures for dealing with IT vulnerabilities
Users of the affected applications should keep them up to date. When security gaps become known, manufacturers are required to fix them as quickly as possible by developing a patch or a workaround. If security patches are available, install them promptly. For information, consult the sources listed in the next section. These often contain further information about the latest version of the software in question as well as the availability of security patches or information about workarounds. If you have any further questions or uncertainties, please contact your responsible administrator. IT security managers should regularly check the sources mentioned to see whether a new security update is available.
Sources of updates, patches and workarounds
Here you will find further links with information about bug reports, security fixes and workarounds.
GitLab Patch Release vom 2024-04-24 (24.04.2024)
For more information, see:
Version history of this security alert
This is the initial version of this IT security notice for GitLab. If updates are announced, this text will be updated. You can read about changes or additions in this version history.
April 24, 2024 – Initial version
+++ Editorial note: This text was generated based on current BSI data and will be updated in a data-driven manner depending on the warning situation. We accept feedback and comments at [email protected]. +++
follow News.de already at Facebook, Twitter, Pinterest and YouTube? Here you will find hot news, current videos and a direct line to the editorial team.
kns/roj/news.de