Home » Microsoft GitHub Enterprise at risk: new security hole! Multiple vulnerabilities reported

Microsoft GitHub Enterprise at risk: new security hole! Multiple vulnerabilities reported

by admin
Microsoft GitHub Enterprise at risk: new security hole!  Multiple vulnerabilities reported

There is a current IT security warning for Microsoft GitHub Enterprise. You can find out what vulnerabilities are involved, which products are affected and what you can do here.

The latest manufacturer recommendations regarding updates, workarounds and security patches for this vulnerability can be found here: GitHub Advisory Database (As of April 21, 2024). Other useful resources are listed later in this article.

Multiple vulnerabilities reported for Microsoft GitHub Enterprise – Risk: High

Risk level: 4 (high)
CVSS Base Score: 8,0
CVSS Temporal Score: 7,0
Remoteangriff: Ja

The Common Vulnerability Scoring System (CVSS) is used to assess the vulnerability of computer systems. The CVSS standard makes it possible to compare potential or actual security vulnerabilities based on various metrics in order to create a priority list for taking 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 vulnerability discussed here is rated as “high” with a base score of 8.0.

Microsoft GitHub Enterprise Bug: Summary of current vulnerabilities

GitHub is a network-based version management service for software development projects.

A remote authenticated attacker could exploit multiple vulnerabilities in Microsoft GitHub Enterprise to execute arbitrary code, bypass security measures, or tamper with files.

The vulnerabilities were classified using the CVE designation system (Common Vulnerabilities and Exposures) by their individual serial numbers CVE-2024-2440, CVE-2024-3470, CVE-2024-3646 und CVE-2024-3684.

Systems affected by the security gap at a glance

operating system

Products
Microsoft GitHub Enterprise Microsoft GitHub Enterprise Microsoft GitHub Enterprise Microsoft GitHub Enterprise

See also  IBM App Connect Enterprise at risk: new security hole! Vulnerability allows cross-site request forgery

General measures for dealing with IT security gaps

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.

GitHub Advisory Database vom 2024-04-21 (21.04.2024)
For more information, see:

GitHub Advisory Database vom 2024-04-21 (21.04.2024)
For more information, see:

Release Notes Enterprise Server 3.10.10 vom 2024-04-21 (21.04.2024)
For more information, see:

Release Notes Enterprise Server 3.10.10 vom 2024-04-21 (21.04.2024)
For more information, see:

Release Notes Enterprise Server 3.11.8 vom 2024-04-21 (21.04.2024)
For more information, see:

Release Notes Enterprise Server 3.10.10 vom 2024-04-21 (21.04.2024)
For more information, see:

Version history of this security alert

This is the initial version of this IT security notice for Microsoft GitHub Enterprise. This text will be updated as updates are announced. You can see the changes made using the version history below.

April 21, 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.

See also  Perseverance persists in deciphering a Martian lake

kns/roj/news.de

You may also like

Leave a Comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.

This website uses cookies to improve your experience. We'll assume you're ok with this, but you can opt-out if you wish. Accept Read More

Privacy & Cookies Policy