Security update for git SUSE Patch security@suse.de SUSE Security Team SUSE-SU-2025:20049-1 Final 1 1 2025-02-03T08:55:36Z current 2025-02-03T08:55:36Z 2025-02-03T08:55:36Z cve-database/bin/generate-cvrf.pl 2017-02-24T01:00:00Z Security update for git This update for git fixes the following issues: git was updated to 2.45.1: * CVE-2024-32002: recursive clones on case-insensitive filesystems that support symbolic links are susceptible to case confusion (bsc#1224168) * CVE-2024-32004: arbitrary code execution during local clones (bsc#1224170) * CVE-2024-32020: file overwriting vulnerability during local clones (bsc#1224171) * CVE-2024-32021: git may create hardlinks to arbitrary user- readable files (bsc#1224172) * CVE-2024-32465: arbitrary code execution during clone operations (bsc#1224173) Update to 2.45.0: * Improved efficiency managing repositories with many references ("git init --ref-format=reftable") * "git checkout -p" and friends learned that that "@" is a synonym for "HEAD" * cli improvements handling refs * Expanded a number of commands and options, UI improvements * status.showUntrackedFiles now accepts "true" * git-cherry-pick(1) now automatically drops redundant commits with new --empty option * The userdiff patterns for C# has been updated. Update to 2.44.0: * "git checkout -B <branch>" now longer allows switching to a branch that is in use on another worktree. The users need to use "--ignore-other-worktrees" option. * Faster server-side rebases with git replay * Faster pack generation with multi-pack reuse * rebase auto-squashing now works in non-interactive mode * pathspec now understands attr, e.g. ':(attr:~binary) for selecting non-binaries, or builtin_objectmode for selecting items by file mode or other properties * Many other cli UI and internal improvements and extensions - Do not replace apparmor configuration, fixes bsc#1216545 Update to 2.43.2: * https://raw.githubusercontent.com/git/git/master/Documentation/RelNotes/2.43.2.txt * Update to a new feature recently added, "git show-ref --exists". * Rename detection logic ignored the final line of a file if it is an incomplete line. * "git diff --no-rename A B" did not disable rename detection but did not trigger an error from the command line parser. * "git diff --no-index file1 file2" segfaulted while invoking the external diff driver, which has been corrected. * A failed "git tag -s" did not necessarily result in an error depending on the crypto backend, which has been corrected. * "git stash" sometimes was silent even when it failed due to unwritable index file, which has been corrected. * Recent conversion to allow more than 0/1 in GIT_FLUSH broke the mechanism by flipping what yes/no means by mistake, which has been corrected. Update to 2.43.1: * https://raw.githubusercontent.com/git/git/master/Documentation/RelNotes/2.43.1.txt - gitweb AppArmor profile: allow reading etc/gitweb-common.conf (bsc#1218664) - git moved to /usr/libexec/git/git, update AppArmor profile accordingly (bsc#1218588) Update to 2.43.0: * The "--rfc" option of "git format-patch" used to be a valid way to override an earlier "--subject-prefix=<something>" on the command line and replace it with "[RFC PATCH]", but from this release, it merely prefixes the string "RFC " in front of the given subject prefix. If you are negatively affected by this change, please use "--subject-prefix=PATCH --rfc" as a replacement. * In Git 2.42, "git rev-list --stdin" learned to take non-revisions (like "--not") from the standard input, but the way such a "--not" was handled was quite confusing, which has been rethought. The updated rule is that "--not" given from the command line only affects revs given from the command line that comes but not revs read from the standard input, and "--not" read from the standard input affects revs given from the standard input and not revs given from the command line. * A message written in olden time prevented a branch from getting checked out, saying it is already checked out elsewhere. But these days, we treat a branch that is being bisected or rebased just like a branch that is checked out and protect it from getting modified with the same codepath. The message has been rephrased to say that the branch is "in use" to avoid confusion. * Hourly and other schedules of "git maintenance" jobs are randomly distributed now. * "git cmd -h" learned to signal which options can be negated by listing such options like "--[no-]opt". * The way authentication related data other than passwords (e.g., oauth token and password expiration data) are stored in libsecret keyrings has been rethought. * Update the libsecret and wincred credential helpers to correctly match which credential to erase; they erased the wrong entry in some cases. * Git GUI updates. * "git format-patch" learned a new "--description-file" option that lets cover letter description to be fed; this can be used on detached HEAD where there is no branch description available, and also can override the branch description if there is one. * Use of the "--max-pack-size" option to allow multiple packfiles to be created is now supported even when we are sending unreachable objects to cruft packs. * "git format-patch --rfc --subject-prefix=<foo>" used to ignore the "--subject-prefix" option and used "[RFC PATCH]"; now we will add "RFC" prefix to whatever subject prefix is specified. * "git log --format" has been taught the %(decorate) placeholder for further customization over what the "--decorate" option offers. * The default log message created by "git revert", when reverting a commit that records a revert, has been tweaked, to encourage people to describe complex "revert of revert of revert" situations better in their own words. * The command-line completion support (in contrib/) learned to complete "git commit --trailer=" for possible trailer keys. * "git update-index" learned the "--show-index-version" option to inspect the index format version used by the on-disk index file. * "git diff" learned the "diff.statNameWidth" configuration variable, to give the default width for the name part in the "--stat" output. * "git range-diff --notes=foo" compared "log --notes=foo --notes" of the two ranges, instead of using just the specified notes tree, which has been corrected to use only the specified notes tree. * The command line completion script (in contrib/) can be told to complete aliases by including ": git <cmd> ;" in the alias to tell it that the alias should be completed in a similar way to how "git <cmd>" is completed. The parsing code for the alias has been loosened to allow ';' without an extra space before it. * "git for-each-ref" and friends learned to apply mailmap to authorname and other fields in a more flexible way than using separate placeholder letters like %a[eElL] every time we want to come up with small variants. * "git repack" machinery learned to pay attention to the "--filter=" option. * "git repack" learned the "--max-cruft-size" option to prevent cruft packs from growing without bounds. * "git merge-tree" learned to take strategy backend specific options via the "-X" option, like "git merge" does. * "git log" and friends learned the "--dd" option that is a short-hand for "--diff-merges=first-parent -p". * The attribute subsystem learned to honor the "attr.tree" configuration variable that specifies which tree to read the .gitattributes files from. * "git merge-file" learns a mode to read three variants of the contents to be merged from blob objects. * see https://raw.githubusercontent.com/git/git/master/Documentation/RelNotes/2.43.0.txt Update 2.42.1: * Fix "git diff" exit code handling The CVRF data is provided by SUSE under the Creative Commons License 4.0 with Attribution (CC-BY-4.0). SUSE-SLE-Micro-6.0-48 Copyright SUSE LLC under the Creative Commons License 4.0 with Attribution (CC-BY-4.0) https://www.suse.com/support/update/announcement/2025/suse-su-202520049-1/ Link for SUSE-SU-2025:20049-1 https://lists.suse.com/pipermail/sle-security-updates/2025-June/021288.html E-Mail link for SUSE-SU-2025:20049-1 https://www.suse.com/support/security/rating/ SUSE Security Ratings https://bugzilla.suse.com/1042640 SUSE Bug 1042640 https://bugzilla.suse.com/1061041 SUSE Bug 1061041 https://bugzilla.suse.com/1069468 SUSE Bug 1069468 https://bugzilla.suse.com/1082023 SUSE Bug 1082023 https://bugzilla.suse.com/1216545 SUSE Bug 1216545 https://bugzilla.suse.com/1218588 SUSE Bug 1218588 https://bugzilla.suse.com/1218664 SUSE Bug 1218664 https://bugzilla.suse.com/1224168 SUSE Bug 1224168 https://bugzilla.suse.com/1224170 SUSE Bug 1224170 https://bugzilla.suse.com/1224171 SUSE Bug 1224171 https://bugzilla.suse.com/1224172 SUSE Bug 1224172 https://bugzilla.suse.com/1224173 SUSE Bug 1224173 https://bugzilla.suse.com/779536 SUSE Bug 779536 https://www.suse.com/security/cve/CVE-2005-4900/ SUSE CVE CVE-2005-4900 page https://www.suse.com/security/cve/CVE-2017-14867/ SUSE CVE CVE-2017-14867 page https://www.suse.com/security/cve/CVE-2024-32002/ SUSE CVE CVE-2024-32002 page https://www.suse.com/security/cve/CVE-2024-32004/ SUSE CVE CVE-2024-32004 page https://www.suse.com/security/cve/CVE-2024-32020/ SUSE CVE CVE-2024-32020 page https://www.suse.com/security/cve/CVE-2024-32021/ SUSE CVE CVE-2024-32021 page https://www.suse.com/security/cve/CVE-2024-32465/ SUSE CVE CVE-2024-32465 page SUSE Linux Micro 6.0 git-2.45.1-1.1 git-core-2.45.1-1.1 perl-Git-2.45.1-1.1 git-2.45.1-1.1 as a component of SUSE Linux Micro 6.0 git-core-2.45.1-1.1 as a component of SUSE Linux Micro 6.0 perl-Git-2.45.1-1.1 as a component of SUSE Linux Micro 6.0 SHA-1 is not collision resistant, which makes it easier for context-dependent attackers to conduct spoofing attacks, as demonstrated by attacks on the use of SHA-1 in TLS 1.2. NOTE: this CVE exists to provide a common identifier for referencing this SHA-1 issue; the existence of an identifier is not, by itself, a technology recommendation. CVE-2005-4900 SUSE Linux Micro 6.0:git-2.45.1-1.1 SUSE Linux Micro 6.0:git-core-2.45.1-1.1 SUSE Linux Micro 6.0:perl-Git-2.45.1-1.1 important 4.3 AV:N/AC:M/Au:N/C:P/I:N/A:N To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520049-1/ https://www.suse.com/security/cve/CVE-2005-4900.html CVE-2005-4900 https://bugzilla.suse.com/1026646 SUSE Bug 1026646 https://bugzilla.suse.com/1026936 SUSE Bug 1026936 https://bugzilla.suse.com/1042640 SUSE Bug 1042640 https://bugzilla.suse.com/1150998 SUSE Bug 1150998 Git before 2.10.5, 2.11.x before 2.11.4, 2.12.x before 2.12.5, 2.13.x before 2.13.6, and 2.14.x before 2.14.2 uses unsafe Perl scripts to support subcommands such as cvsserver, which allows attackers to execute arbitrary OS commands via shell metacharacters in a module name. The vulnerable code is reachable via git-shell even without CVS support. CVE-2017-14867 SUSE Linux Micro 6.0:git-2.45.1-1.1 SUSE Linux Micro 6.0:git-core-2.45.1-1.1 SUSE Linux Micro 6.0:perl-Git-2.45.1-1.1 important 7.2 AV:L/AC:L/Au:N/C:C/I:C/A:C 9 AV:N/AC:L/Au:S/C:C/I:C/A:C To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520049-1/ https://www.suse.com/security/cve/CVE-2017-14867.html CVE-2017-14867 https://bugzilla.suse.com/1060377 SUSE Bug 1060377 https://bugzilla.suse.com/1060378 SUSE Bug 1060378 https://bugzilla.suse.com/1061041 SUSE Bug 1061041 Git is a revision control system. Prior to versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4, repositories with submodules can be crafted in a way that exploits a bug in Git whereby it can be fooled into writing files not into the submodule's worktree but into a `.git/` directory. This allows writing a hook that will be executed while the clone operation is still running, giving the user no opportunity to inspect the code that is being executed. The problem has been patched in versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4. If symbolic link support is disabled in Git (e.g. via `git config --global core.symlinks false`), the described attack won't work. As always, it is best to avoid cloning repositories from untrusted sources. CVE-2024-32002 SUSE Linux Micro 6.0:git-2.45.1-1.1 SUSE Linux Micro 6.0:git-core-2.45.1-1.1 SUSE Linux Micro 6.0:perl-Git-2.45.1-1.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520049-1/ https://www.suse.com/security/cve/CVE-2024-32002.html CVE-2024-32002 https://bugzilla.suse.com/1224168 SUSE Bug 1224168 https://bugzilla.suse.com/1224170 SUSE Bug 1224170 Git is a revision control system. Prior to versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4, an attacker can prepare a local repository in such a way that, when cloned, will execute arbitrary code during the operation. The problem has been patched in versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4. As a workaround, avoid cloning repositories from untrusted sources. CVE-2024-32004 SUSE Linux Micro 6.0:git-2.45.1-1.1 SUSE Linux Micro 6.0:git-core-2.45.1-1.1 SUSE Linux Micro 6.0:perl-Git-2.45.1-1.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520049-1/ https://www.suse.com/security/cve/CVE-2024-32004.html CVE-2024-32004 https://bugzilla.suse.com/1224170 SUSE Bug 1224170 Git is a revision control system. Prior to versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4, local clones may end up hardlinking files into the target repository's object database when source and target repository reside on the same disk. If the source repository is owned by a different user, then those hardlinked files may be rewritten at any point in time by the untrusted user. Cloning local repositories will cause Git to either copy or hardlink files of the source repository into the target repository. This significantly speeds up such local clones compared to doing a "proper" clone and saves both disk space and compute time. When cloning a repository located on the same disk that is owned by a different user than the current user we also end up creating such hardlinks. These files will continue to be owned and controlled by the potentially-untrusted user and can be rewritten by them at will in the future. The problem has been patched in versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4. CVE-2024-32020 SUSE Linux Micro 6.0:git-2.45.1-1.1 SUSE Linux Micro 6.0:git-core-2.45.1-1.1 SUSE Linux Micro 6.0:perl-Git-2.45.1-1.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520049-1/ https://www.suse.com/security/cve/CVE-2024-32020.html CVE-2024-32020 https://bugzilla.suse.com/1224171 SUSE Bug 1224171 Git is a revision control system. Prior to versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4, when cloning a local source repository that contains symlinks via the filesystem, Git may create hardlinks to arbitrary user-readable files on the same filesystem as the target repository in the `objects/` directory. Cloning a local repository over the filesystem may creating hardlinks to arbitrary user-owned files on the same filesystem in the target Git repository's `objects/` directory. When cloning a repository over the filesystem (without explicitly specifying the `file://` protocol or `--no-local`), the optimizations for local cloning will be used, which include attempting to hard link the object files instead of copying them. While the code includes checks against symbolic links in the source repository, which were added during the fix for CVE-2022-39253, these checks can still be raced because the hard link operation ultimately follows symlinks. If the object on the filesystem appears as a file during the check, and then a symlink during the operation, this will allow the adversary to bypass the check and create hardlinks in the destination objects directory to arbitrary, user-readable files. The problem has been patched in versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4. CVE-2024-32021 SUSE Linux Micro 6.0:git-2.45.1-1.1 SUSE Linux Micro 6.0:git-core-2.45.1-1.1 SUSE Linux Micro 6.0:perl-Git-2.45.1-1.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520049-1/ https://www.suse.com/security/cve/CVE-2024-32021.html CVE-2024-32021 https://bugzilla.suse.com/1224172 SUSE Bug 1224172 Git is a revision control system. The Git project recommends to avoid working in untrusted repositories, and instead to clone it first with `git clone --no-local` to obtain a clean copy. Git has specific protections to make that a safe operation even with an untrusted source repository, but vulnerabilities allow those protections to be bypassed. In the context of cloning local repositories owned by other users, this vulnerability has been covered in CVE-2024-32004. But there are circumstances where the fixes for CVE-2024-32004 are not enough: For example, when obtaining a `.zip` file containing a full copy of a Git repository, it should not be trusted by default to be safe, as e.g. hooks could be configured to run within the context of that repository. The problem has been patched in versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4. As a workaround, avoid using Git in repositories that have been obtained via archives from untrusted sources. CVE-2024-32465 SUSE Linux Micro 6.0:git-2.45.1-1.1 SUSE Linux Micro 6.0:git-core-2.45.1-1.1 SUSE Linux Micro 6.0:perl-Git-2.45.1-1.1 important To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". https://www.suse.com/support/update/announcement/2025/suse-su-202520049-1/ https://www.suse.com/security/cve/CVE-2024-32465.html CVE-2024-32465 https://bugzilla.suse.com/1224170 SUSE Bug 1224170 https://bugzilla.suse.com/1224173 SUSE Bug 1224173