Threats affecting pkg:brew/nbdime

GitPython versions before 4.0.4_6 contain unguarded forwarding of git command options in the IndexFile.checkout() and TagReference.create() methods. This allows an attacker with repository write access to cause arbitrary file overwrites outside the repository via the --prefix option in checkout-index, or to read arbitrary files on the system via the -F/--file option in git tag. Both issues arise because these methods forward **kwargs directly to git commands without proper safety checks. A fix is available in version 4.0.4_6.

GitPython's Repo.archive() method uses a denylist to block unsafe git archive options that could lead to arbitrary command execution or file writes. However, this denylist is incomplete and omits the --add-file and --add-virtual-file options, which allow an attacker to read arbitrary files from the filesystem and inject attacker-controlled content into archives. This flaw enables arbitrary file read at the privileges of the process using GitPython. A fix is available in version 4.0.4_6.

A vulnerability in GitPython's config_writer() allows an attacker to inject newline characters into the section parameter, bypassing the patch for CVE-2026-42215. This enables writing arbitrary section headers into the .git/config file, including a malicious [core] section with hooksPath pointing to an attacker-controlled directory. When a git hook is triggered, this leads to remote code execution (RCE). The issue affects GitPython versions from 1.1.0 up to but not including 4.0.4_3, where it has been fixed.

GitPython version 3.1.50 contains a vulnerability where the default unsafe-option gate intended to block dangerous git clone options can be bypassed using joined short-option forms such as '-u<helper>'. This allows execution of local commands via Git's upload-pack option despite the default safety settings. The issue arises because the option canonicalization does not recognize joined short options correctly, leading to a residual security bypass.

GitPython versions from 1.1.0 up to but not including 4.0.4_4 contain command injection vulnerabilities due to insufficient validation of user-supplied options in several Git command wrappers, including Repo.archive(), git.ls_remote(), and others. This allows an attacker to execute arbitrary commands or cause file truncation by crafting malicious arguments. The issue arises because certain keyword arguments are transformed into Git command options without proper sanitization, enabling injection of commands via options like --exec or upload-pack. A fix is available in version 4.0.4_4.

GitPython versions up to 3.1.50 contain a vulnerability in the Repo.clone_from() method where the remote URL is passed through os.path.expandvars() without restriction. This causes environment variables in the URL to be expanded server-side, potentially leaking sensitive environment variables such as AWS_SECRET_ACCESS_KEY or GITHUB_TOKEN to attacker-controlled hosts. The vulnerability arises because polish_url() applies environment variable expansion indiscriminately to URLs, and no scheme check or opt-out exists. A fix is available in version 4.0.4_4.

GitPython's config_writer().set_value() method does not validate input values for newline characters, allowing injection of a malicious core.hooksPath configuration. This enables an attacker to control Git hook execution paths, potentially leading to remote code execution during Git operations that invoke hooks. The vulnerability affects GitPython versions from 1.1.0 up to but not including 4.0.4_2. A fix is available in version 4.0.4_2 that rejects values containing CR, LF, or NUL characters.

GitPython versions >=1.1.0 and <4.0.4_2 contain a vulnerability in the handling of multi_options in clone operations. The code validates the original multi_options list but executes a transformed version after splitting, allowing an attacker to embed unsafe options like '--config core.hooksPath' that bypass validation. This can lead to execution of attacker-controlled Git hooks during cloning or submodule updates.

GitPython versions from 3.1.1_1 up to but not including 4.0.4_2 contain a command injection vulnerability via unsafe handling of certain Git options passed as Python keyword arguments. The vulnerability arises because the safety check blocks dangerous Git options only when passed with hyphenated names, but not when passed using underscore-form kwargs, which are later converted to the dangerous flags. This allows attacker-controlled input to execute arbitrary commands during Git operations such as clone, fetch, pull, and push. A fix is available in version 4.0.4_2.

GitPython versions up to 3.1.52 contain a vulnerability where attacker-controlled submodule names can inject arbitrary Git configuration directives by exploiting insufficient escaping of section names. This allows injection of directives such as core.sshCommand, potentially leading to remote code execution on the victim's next Git operation. The issue arises because only CR, LF, and NUL characters are blocked in config names, but special characters like ] and [ are not escaped, enabling same-line section injection. A fix is available in GitPython 4.0.4_4.

GitPython versions from 1.1.0 up to but not including 4.0.4_4 contain a command injection vulnerability (CVE-2026-67325) due to incomplete blocking of unsafe git options. The vulnerability arises because the fix for a previous issue (CVE-2026-42215) only blocked exact matches of dangerous options but did not account for git's acceptance of unambiguous long-option prefix abbreviations. This allows attackers controlling keyword argument keys to bypass the blocklist and execute arbitrary commands during clone, fetch, pull, or push operations. A fix is available in version 4.0.4_4.

A path traversal vulnerability in GitPython reference APIs allows attackers who can supply crafted reference paths to write, overwrite, move, or delete files outside the repository's .git directory. This occurs due to insufficient validation of reference paths before filesystem write, rename, and delete operations. The flaw affects GitPython versions up to 3.1.46 and the current main branch (3.1.47 locally).

CVE-2024-22190 is a vulnerability in nbdime affecting Windows platforms where GitPython uses an untrusted search path to run git or bash.exe, allowing arbitrary code execution. This occurs when GitPython runs git commands through a shell or runs hook scripts using bash.exe without properly restricting the search path. Malicious executables named git.exe or bash.exe placed in a repository or working directory can be executed unintentionally. The vulnerability is a partial regression of CVE-2023-40590 and affects nbdime versions from 1.1.0 up to but not including 4.0.1_1. A fix is available in version 4.0.1_1.