Improper Ownership Management Affecting git-core package, versions <2.26.2-150000.41.1


Severity

Recommended
0.0
high
0
10

Based on SUSE Linux Enterprise Server security rating.

Threat Intelligence

EPSS
0.05% (19th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-SLES151-GITCORE-2959425
  • published23 Jul 2022
  • disclosed22 Jul 2022

Introduced: 22 Jul 2022

CVE-2022-29187  (opens in a new tab)
CWE-282  (opens in a new tab)
CWE-427  (opens in a new tab)

How to fix?

Upgrade SLES:15.1 git-core to version 2.26.2-150000.41.1 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream git-core package and not the git-core package as distributed by SLES. See How to fix? for SLES:15.1 relevant fixed versions and status.

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.

References

CVSS Scores

version 3.1