File CVE-2024-32002.patch of Package git.34091

commit 97065761333fd62db1912d81b489db938d8c991d
Author: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Date:   Fri Mar 22 11:19:22 2024 +0100

    submodules: submodule paths must not contain symlinks
    
    When creating a submodule path, we must be careful not to follow
    symbolic links. Otherwise we may follow a symbolic link pointing to
    a gitdir (which are valid symbolic links!) e.g. while cloning.
    
    On case-insensitive filesystems, however, we blindly replace a directory
    that has been created as part of the `clone` operation with a symlink
    when the path to the latter differs only in case from the former's path.
    
    Let's simply avoid this situation by expecting not ever having to
    overwrite any existing file/directory/symlink upon cloning. That way, we
    won't even replace a directory that we just created.
    
    This addresses CVE-2024-32002.
    
    Reported-by: Filip Hejsek <filip.hejsek@gmail.com>
    Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>

Index: git-2.26.2/builtin/submodule--helper.c
===================================================================
--- git-2.26.2.orig/builtin/submodule--helper.c
+++ git-2.26.2/builtin/submodule--helper.c
@@ -1233,10 +1233,33 @@ static int module_deinit(int argc, const
 	return 0;
 }
 
+static int dir_contains_only_dotgit(const char *path)
+{
+	DIR *dir = opendir(path);
+	struct dirent *e;
+	int ret = 1;
+
+	if (!dir)
+		return 0;
+
+	e = readdir_skip_dot_and_dotdot(dir);
+	if (!e)
+		ret = 0;
+	else if (strcmp(DEFAULT_GIT_DIR_ENVIRONMENT, e->d_name) ||
+		 (e = readdir_skip_dot_and_dotdot(dir))) {
+		error("unexpected item '%s' in '%s'", e->d_name, path);
+		ret = 0;
+	}
+
+	closedir(dir);
+	return ret;
+}
+
 static int clone_submodule(const char *path, const char *gitdir, const char *url,
 			   const char *depth, struct string_list *reference, int dissociate,
 			   int quiet, int progress, int single_branch)
 {
+	struct stat st;
 	struct child_process cp = CHILD_PROCESS_INIT;
 
 	argv_array_push(&cp.args, "clone");
Index: git-2.26.2/t/t7406-submodule-update.sh
===================================================================
--- git-2.26.2.orig/t/t7406-submodule-update.sh
+++ git-2.26.2/t/t7406-submodule-update.sh
@@ -1006,4 +1006,52 @@ test_expect_success 'git clone passes th
 	rm -rf super4
 '
 
+test_expect_success CASE_INSENSITIVE_FS,SYMLINKS \
+	'submodule paths must not follow symlinks' '
+
+	# This is only needed because we want to run this in a self-contained
+	# test without having to spin up an HTTP server; However, it would not
+	# be needed in a real-world scenario where the submodule is simply
+	# hosted on a public site.
+	test_config_global protocol.file.allow always &&
+
+	# Make sure that Git tries to use symlinks on Windows
+	test_config_global core.symlinks true &&
+
+	tell_tale_path="$PWD/tell.tale" &&
+	git init hook &&
+	(
+		cd hook &&
+		mkdir -p y/hooks &&
+		write_script y/hooks/post-checkout <<-EOF &&
+		echo HOOK-RUN >&2
+		echo hook-run >"$tell_tale_path"
+		EOF
+		git add y/hooks/post-checkout &&
+		test_tick &&
+		git commit -m post-checkout
+	) &&
+
+	hook_repo_path="$(pwd)/hook" &&
+	git init captain &&
+	(
+		cd captain &&
+		git submodule add --name x/y "$hook_repo_path" A/modules/x &&
+		test_tick &&
+		git commit -m add-submodule &&
+
+		printf .git >dotgit.txt &&
+		git hash-object -w --stdin <dotgit.txt >dot-git.hash &&
+		printf "120000 %s 0\ta\n" "$(cat dot-git.hash)" >index.info &&
+		git update-index --index-info <index.info &&
+		test_tick &&
+		git commit -m add-symlink
+	) &&
+
+	test_path_is_missing "$tell_tale_path" &&
+	test_must_fail git clone --recursive captain hooked 2>err &&
+	grep "directory not empty" err &&
+	test_path_is_missing "$tell_tale_path"
+'
+
 test_done