GitPython computes the on-disk location for submodules from the .gitmodules section name without validating it. An attacker can craft a repository with a submodule name containing path traversal sequences (e.g., '../../../../some/path'), causing GitPython to create and initialize a full Git repository outside the intended clone directory when submodule initialization is performed. This vulnerability arises because GitPython's implementation does not normalize or validate the submodule name before using it to construct filesystem paths, unlike core Git which blocks such attacks (CVE-2018-11235). The attack requires the victim to clone the malicious repository and run submodule update with init=True. Proof-of-concept demonstrates creation of repositories outside the working tree. The vulnerability affects GitPython versions used in Snowflake CLI >=3.4.1 and <3.25.0. A patch is available.

An attacker controlling a Git repository that a victim clones and initializes submodules for using GitPython can cause arbitrary creation and initialization of Git repositories at attacker-chosen filesystem paths outside the intended working directory. This can lead to integrity issues by placing Git metadata and repositories in unexpected locations. There is no direct confidentiality or availability impact described. The vulnerability requires user interaction (cloning and submodule initialization) and user-level permissions. Core Git is not affected due to prior mitigations.

A patch is available for this vulnerability. Users of affected GitPython versions in Snowflake CLI (>=3.4.1 <3.25.0) should upgrade to a fixed version as soon as possible. Until patched, avoid cloning and initializing submodules from untrusted repositories using GitPython. The vendor advisory confirms patch availability; apply the official fix to remediate this issue.