Git up to 2.37.0 access control

Summaryinfo

A vulnerability was found in Git up to 2.37.0. It has been classified as critical. Affected by this vulnerability is an unknown functionality. Performing a manipulation results in access control. This vulnerability is known as CVE-2022-29187. Remote exploitation of the attack is possible. No exploit is available. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability was found in Git up to 2.37.0 (Versioning Software). It has been classified as critical. This affects an unknown code block. The manipulation with an unknown input leads to a access control vulnerability. CWE is classifying the issue as CWE-284. The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

Git is a distributed revision control system. Git prior to versions 2.37.1, 2.36.2, 2.35.4, 2.34.4, 2.33.4, 2.32.3, 2.31.4, and 2.30.5, is vulnerable to privilege escalation in all platforms. An unsuspecting user could still be affected by the issue reported in CVE-2022-24765, for example when navigating as root into a shared tmp directory that is owned by them, but where an attacker could create a git repository. Versions 2.37.1, 2.36.2, 2.35.4, 2.34.4, 2.33.4, 2.32.3, 2.31.4, and 2.30.5 contain a patch for this issue. The simplest way to avoid being affected by the exploit described in the example is to avoid running git as root (or an Administrator in Windows), and if needed to reduce its use to a minimum. While a generic workaround is not possible, a system could be hardened from the exploit described in the example by removing any such repository if it exists already and creating one as root to block any future attacks.

The weakness was published 07/13/2022 as GHSA-j342-m5hw-rr3v. It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2022-29187 since 04/13/2022. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1068 according to MITRE ATT&CK.

Upgrading to version 2.30.5, 2.31.4, 2.32.3, 2.33.4, 2.34.4, 2.35.4, 2.36.2 or 2.37.1 eliminates this vulnerability.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2022-33581). Be aware that VulDB is the high quality source for vulnerability data.

Productinfo

Type

• Versioning Software

Name

• Git

Version

• 2.0
• 2.1
• 2.2
• 2.3
• 2.4
• 2.5
• 2.6
• 2.7
• 2.8
• 2.9
• 2.10
• 2.11
• 2.12
• 2.13
• 2.14
• 2.15
• 2.16
• 2.17
• 2.18
• 2.19
• 2.20
• 2.21
• 2.22
• 2.23
• 2.24
• 2.25
• 2.26
• 2.27
• 2.28
• 2.29
• 2.30
• 2.30.0
• 2.30.1
• 2.30.2
• 2.30.3
• 2.30.4
• 2.31
• 2.31.0
• 2.31.1
• 2.31.2
• 2.31.3
• 2.32
• 2.32.0
• 2.32.1
• 2.32.2
• 2.33
• 2.33.0
• 2.33.1
• 2.33.2
• 2.33.3
• 2.34
• 2.34.0
• 2.34.1
• 2.34.2
• 2.34.3
• 2.35
• 2.35.0
• 2.35.1
• 2.35.2
• 2.35.3
• 2.36
• 2.36.0
• 2.36.1
• 2.37.0

License

• open-source

Website

• Product: https://github.com/git/git/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Be aware that VulDB is the high quality source for vulnerability data.

Discussion