CVE-2023-23946

Git, a revision control system, is vulnerable to path traversal prior to versions 2.39.2, 2.38.4, 2.37.6, 2.36.5, 2.35.7, 2.34.7, 2.33.7, 2.32.6, 2.31.7, and 2.30.8. By feeding a crafted input to git apply, a path outside the working tree can be overwritten as the user who is running git apply. A fix has been prepared and will appear in v2.39.2, v2.38.4, v2.37.6, v2.36.5, v2.35.7, v2.34.7, v2.33.7, v2.32.6, v2.31.7, and v2.30.8. As a workaround, use git apply --stat to inspect a patch before applying; avoid applying one that creates a symbolic link and then creates a file beyond the symbolic link.

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 a revision control system. Using a specially-crafted repository, Git prior to versions 2.39.2, 2.38.4, 2.37.6, 2.36.5, 2.35.7, 2.34.7, 2.33.7, 2.32.6, 2.31.7, and 2.30.8 can be tricked into using its local clone optimization even when using a non-local transport. Though Git will abort local clones whose source $GIT_DIR/objects directory contains symbolic links, the objects directory itself may still be a symbolic link. These two may be combined to include arbitrary files based on known paths on the victim's filesystem within the malicious repository's working copy, allowing for data exfiltration in a similar manner as CVE-2022-39253. A fix has been prepared and will appear in v2.39.2 v2.38.4 v2.37.6 v2.36.5 v2.35.7 v2.34.7 v2.33.7 v2.32.6, v2.31.7 and v2.30.8. If upgrading is impractical, two short-term workarounds are available. Avoid cloning repositories from untrusted sources with --recurse-submodules. Instead, consider cloning repositories without recursively cloning their submodules, and instead run git submodule update at each layer. Before doing so, inspect each new .gitmodules file to ensure that it does not contain suspicious module URLs.(CVE-2023-22490)

Git, a revision control system, is vulnerable to path traversal prior to versions 2.39.2, 2.38.4, 2.37.6, 2.36.5, 2.35.7, 2.34.7, 2.33.7, 2.32.6, 2.31.7, and 2.30.8. By feeding a crafted input to git apply, a path outside the working tree can be overwritten as the user who is running git apply. A fix has been prepared and will appear in v2.39.2, v2.38.4, v2.37.6, v2.36.5, v2.35.7, v2.34.7, v2.33.7, v2.32.6, v2.31.7, and v2.30.8. As a workaround, use git apply --stat to inspect a patch before applying; avoid applying one that creates a symbolic link and then creates a file beyond the symbolic link.(CVE-2023-23946)

Git, a revision control system, is vulnerable to path traversal prior to versions 2.39.2, 2.38.4, 2.37.6, 2.36.5, 2.35.7, 2.34.7, 2.33.7, 2.32.6, 2.31.7, and 2.30.8. By feeding a crafted input to git apply, a path outside the working tree can be overwritten as the user who is running git apply. A fix has been prepared and will appear in v2.39.2, v2.38.4, v2.37.6, v2.36.5, v2.35.7, v2.34.7, v2.33.7, v2.32.6, v2.31.7, and v2.30.8. As a workaround, use git apply --stat to inspect a patch before applying; avoid applying one that creates a symbolic link and then creates a file beyond the symbolic link.

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: by feeding specially crafted input to git apply --reject, a path outside the working tree can be overwritten with partially controlled contents (CVE-2023-25652)
• git: arbitrary configuration injection when renaming or deleting a section from a configuration file (CVE-2023-29007)
• git: data exfiltration with maliciously crafted repository (CVE-2023-22490)
• git: git apply: a path outside the working tree can be overwritten with crafted input (CVE-2023-23946)
• git: malicious placement of crafted messages when git was compiled with runtime prefix (CVE-2023-25815)

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.

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: by feeding specially crafted input to git apply --reject, a path outside the working tree can be overwritten with partially controlled contents (CVE-2023-25652)
• git: arbitrary configuration injection when renaming or deleting a section from a configuration file (CVE-2023-29007)
• git: data exfiltration with maliciously crafted repository (CVE-2023-22490)
• git: git apply: a path outside the working tree can be overwritten with crafted input (CVE-2023-23946)
• git: malicious placement of crafted messages when git was compiled with runtime prefix (CVE-2023-25815)

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.

• 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-2023-23946: apply - fix writing behind newly created symbolic links

Using a specially-crafted repository, Git can be tricked into using its local clone optimization even when using a non-local transport. Though Git will abort local clones whose source $GIT_DIR/objects directory contains symbolic links, the objects directory itself may still be a symbolic link. These two may be combined to include arbitrary files based on known paths on the victim's filesystem within the malicious repository's working copy, allowing for data exfiltration in a similar manner as CVE-2022-39253 (CVE-2023-22490).

By feeding a crafted input to "git apply", a path outside the working tree can be overwritten as the user who is running "git apply" (CVE-2023-23946).

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

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: by feeding specially crafted input to git apply --reject, a path outside the working tree can be overwritten with partially controlled contents (CVE-2023-25652)

• git: arbitrary configuration injection when renaming or deleting a section from a configuration file (CVE-2023-29007)

• git: data exfiltration with maliciously crafted repository (CVE-2023-22490)

• git: git apply: a path outside the working tree can be overwritten with crafted input (CVE-2023-23946)

• git: malicious placement of crafted messages when git was compiled with runtime prefix (CVE-2023-25815)

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.

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).

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).

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).

It was discovered that Git incorrectly handled certain repositories. An attacker could use this issue to make Git uses its local clone optimization even when using a non-local transport. (CVE-2023-22490)

Joern Schneeweisz discovered that Git incorrectly handled certain commands. An attacker could possibly use this issue to overwrite a patch outside the working tree. (CVE-2023-23946)