CVE-2022-39260

Git is an open source, scalable, distributed revision control system. git shell is a restricted login shell that can be used to implement Git's push/pull functionality via SSH. In versions prior to 2.30.6, 2.31.5, 2.32.4, 2.33.5, 2.34.5, 2.35.5, 2.36.3, and 2.37.4, the function that splits the command arguments into an array improperly uses an int to represent the number of entries in the array, allowing a malicious actor to intentionally overflow the return value, leading to arbitrary heap writes. Because the resulting array is then passed to execv(), it is possible to leverage this attack to gain remote code execution on a victim machine. Note that a victim must first allow access to git shell as a login shell in order to be vulnerable to this attack. This problem is patched in versions 2.30.6, 2.31.5, 2.32.4, 2.33.5, 2.34.5, 2.35.5, 2.36.3, and 2.37.4 and users are advised to upgrade to the latest version. Disabling git shell access via remote logins is a viable short-term workaround.

Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency.Git is easy to learn and has a tiny footprint with lightning fast performance. It outclasses SCM tools like Subversion, CVS, Perforce,and ClearCase with features like cheap local branching, convenient staging areas, and multiple workflows.

Security Fix(es):

Git is an open source, scalable, distributed revision control system. Versions prior to 2.30.6, 2.31.5, 2.32.4, 2.33.5, 2.34.5, 2.35.5, 2.36.3, and 2.37.4 are subject to exposure of sensitive information to a malicious actor. When performing a local clone (where the source and target of the clone are on the same volume), Git copies the contents of the source's $GIT_DIR/objects directory into the destination by either creating hardlinks to the source contents, or copying them (if hardlinks are disabled via --no-hardlinks). A malicious actor could convince a victim to clone a repository with a symbolic link pointing at sensitive information on the victim's machine. This can be done either by having the victim clone a malicious repository on the same machine, or having them clone a malicious repository embedded as a bare repository via a submodule from any source, provided they clone with the --recurse-submodules option. Git does not create symbolic links in the $GIT_DIR/objects directory. The problem has been patched in the versions published on 2022-10-18, and backported to v2.30.x. Potential workarounds: Avoid cloning untrusted repositories using the --local optimization when on a shared machine, either by passing the --no-local option to git clone or cloning from a URL that uses the file:// scheme. Alternatively, avoid cloning repositories from untrusted sources with --recurse-submodules or run git config --global protocol.file.allow user.(CVE-2022-39253)

Git is an open source, scalable, distributed revision control system. git shell is a restricted login shell that can be used to implement Git's push/pull functionality via SSH. In versions prior to 2.30.6, 2.31.5, 2.32.4, 2.33.5, 2.34.5, 2.35.5, 2.36.3, and 2.37.4, the function that splits the command arguments into an array improperly uses an int to represent the number of entries in the array, allowing a malicious actor to intentionally overflow the return value, leading to arbitrary heap writes. Because the resulting array is then passed to execv(), it is possible to leverage this attack to gain remote code execution on a victim machine. Note that a victim must first allow access to git shell as a login shell in order to be vulnerable to this attack. This problem is patched in versions 2.30.6, 2.31.5, 2.32.4, 2.33.5, 2.34.5, 2.35.5, 2.36.3, and 2.37.4 and users are advised to upgrade to the latest version. Disabling git shell access via remote logins is a viable short-term workaround.(CVE-2022-39260)

Git is an open source, scalable, distributed revision control system. git shell is a restricted login shell that can be used to implement Git's push/pull functionality via SSH. In versions prior to 2.30.6, 2.31.5, 2.32.4, 2.33.5, 2.34.5, 2.35.5, 2.36.3, and 2.37.4, the function that splits the command arguments into an array improperly uses an int to represent the number of entries in the array, allowing a malicious actor to intentionally overflow the return value, leading to arbitrary heap writes. Because the resulting array is then passed to execv(), it is possible to leverage this attack to gain remote code execution on a victim machine. Note that a victim must first allow access to git shell as a login shell in order to be vulnerable to this attack. This problem is patched in versions 2.30.6, 2.31.5, 2.32.4, 2.33.5, 2.34.5, 2.35.5, 2.36.3, and 2.37.4 and users are advised to upgrade to the latest version. Disabling git shell access via remote logins is a viable short-term workaround.

Git is a distributed revision control system with a decentralized architecture. As opposed to centralized version control systems with a client-server model, Git ensures that each working copy of a Git repository is an exact copy with complete revision history. This not only allows the user to work on and contribute to projects without the need to have permission to push the changes to their official repositories, but also makes it possible for the user to work with no network connection.

Security Fix(es):

• git: On multi-user machines Git users might find themselves unexpectedly in a Git worktree (CVE-2022-24765)
• git: Bypass of safe.directory protections (CVE-2022-29187)
• git: exposure of sensitive information to a malicious actor (CVE-2022-39253)
• git: git shell function that splits command arguments can lead to arbitrary heap writes. (CVE-2022-39260)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

Additional Changes:

For detailed information on changes in this release, see the AlmaLinux Release Notes linked from the References section.

Git is a distributed revision control system with a decentralized architecture. As opposed to centralized version control systems with a client-server model, Git ensures that each working copy of a Git repository is an exact copy with complete revision history. This not only allows the user to work on and contribute to projects without the need to have permission to push the changes to their official repositories, but also makes it possible for the user to work with no network connection.

Security Fix(es):

• git: On multi-user machines Git users might find themselves unexpectedly in a Git worktree (CVE-2022-24765)
• git: Bypass of safe.directory protections (CVE-2022-29187)
• git: exposure of sensitive information to a malicious actor (CVE-2022-39253)
• git: git shell function that splits command arguments can lead to arbitrary heap writes. (CVE-2022-39260)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

Additional Changes:

For detailed information on changes in this release, see the AlmaLinux Release Notes linked from the References section.

• CVE-2022-41903: fix out-of-bounds write caused by integer overflow
• CVE-2021-40330: forbid newlines in host and path
• CVE-2022-39260: reject too long command line strings
• CVE-2021-23521: implement size checks for .gitattributes
• CVE-2023-22490: prevent arbitrary path exfiltration when using non-local transports
• CVE-2023-23946: prevent git-apply from writing behind newly created symbolic links

• CVE-2022-41903: fix out-of-bounds write caused by integer overflow
• CVE-2021-40330: forbid newlines in host and path
• CVE-2022-39260: reject too long command line strings
• CVE-2021-23521: implement size checks for .gitattributes
• CVE-2023-22490: prevent arbitrary path exfiltration when using non-local transports
• CVE-2023-23946: prevent git-apply from writing behind newly created symbolic links

• CVE-2022-41903: fix out-of-bounds write caused by integer overflow
• CVE-2021-40330: forbid newlines in host and path
• CVE-2022-39260: reject too long command line strings
• CVE-2023-23946: prevent git-apply from writing behind newly created symbolic links

• SECURITY UPDATE: out-of-bounds write caused by integer overflow
  • debian/patches/CVE-2022-41903.patch: use 'size_t' instead of 'int' to track the string lengths and so allow >2GB input sizes.
  • CVE-2022-41903
  • t-mark-submodule-clean-test-as-known-failure.patch: mark submodule clean test as known failure and so pass 'make test'.
• SECURITY UPDATE: possible cross-protocol requests
  • debian/patches/CVE-2021-40330.patch: forbid newlines in host and path.
  • CVE-2021-40330
• SECURITY UPDATE: out-of-bounds write and possible RCE caused by integer overflow
  • debian/patches/CVE-2022-39260.patch: reject too long command line strings in split_cmdline().
  • CVE-2022-39260
• SECURITY UPDATE: out-of-bounds write when reading an unreasonably large .gitattributes file
  • debian/patches/CVE-2021-23521.patch: implement line and overall size checks for .gitattributes files.
  • CVE-2021-23521
• SECURITY UPDATE: possible write outside of the repository's working directory
  • debian/patches/CVE-2023-23946.patch: prevent git-apply from writing behind newly created symbolic links.
  • CVE-2023-23946

• CVE-2022-41903: fix out-of-bounds write caused by integer overflow
• CVE-2021-40330: forbid newlines in host and path
• CVE-2022-39260: reject too long command line strings
• CVE-2023-23946: prevent git-apply from writing behind newly created symbolic links

• CVE-2021-40330: forbid newlines in host and path in git_connect()
• CVE-2022-39260: shell - limit size of interactive commands

CVE-2022-39253: A malicious actor could convince a victim to clone a repository with a symbolic link pointing at sensitive information on the victim's machine. CVE-2022-39260: Allowing a malicious actor to intentionally overflow the return value, leading to arbitrary heap writes. CVE-2022-29187: privilege escalation

These are all security issues fixed in the git-2.38.1-1.1 package on the GA media of openSUSE Tumbleweed.

This update for git fixes the following issues:

• CVE-2022-39260: Fixed overflow in split_cmdline() (bsc#1204456).
• CVE-2022-39253: Fixed dereference issue with symbolic links via the --local clone mechanism (bsc#1204455).

This update for git fixes the following issues:

• CVE-2022-39260: Fixed overflow in split_cmdline() (bsc#1204456).
• CVE-2022-39253: Fixed dereference issue with symbolic links via the --local clone mechanism (bsc#1204455).

This update for git fixes the following issues:

• CVE-2023-22490: Fixed incorrectly usable local clone optimization even when using a non-local transport (bsc#1208027).
• CVE-2023-23946: Fixed issue where a path outside the working tree can be overwritten as the user who is running 'git apply' (bsc#1208028).
• CVE-2022-39260: Fixed overflow in split_cmdline(), leading to arbitrary heap writes and remote code execution (bsc#1204456).
• CVE-2022-39253: Fixed dereference issue with symbolic links via the --local clone mechanism (bsc#1204455).

Cory Snider discovered that Git incorrectly handled certain symbolic links. An attacker could possibly use this issue to cause an unexpected behaviour. (CVE-2022-39253)

Kevin Backhouse discovered that Git incorrectly handled certain command strings. An attacker could possibly use this issue to arbitrary code execution. (CVE-2022-39260)

USN-5686-1 fixed several vulnerabilities in Git. This update provides the corresponding fix for CVE-2022-39260 on Ubuntu 16.04 ESM.

Original advisory details:

Kevin Backhouse discovered that Git incorrectly handled certain command strings. An attacker could possibly use this issue to cause a crash or arbitrary code execution.