Threats tagged 'homebrew'

GitPython versions up to 1.2.0.post0_14 contain a vulnerability in the option guard mechanism that allows bypassing the unsafe git option check when using split_single_char_options=False. This bypass enables arbitrary OS command execution via crafted short-option tokens, affecting multiple guarded methods such as clone and fetch. The flaw is an incomplete fix of a previous vulnerability and arises because the guard does not inspect joined short-option tokens emitted when split_single_char_options is False.

GitPython's Repo.init method forwards keyword arguments directly to git init without guarding unsafe options like --template. This allows an attacker who can control the template argument and stage a malicious hooks directory to plant executable git hooks in the new repository. These hooks execute arbitrary code on the next git operation performed by the host process. The vulnerability affects GitPython versions prior to 1.2.0.post0_14 and requires attacker control over the template path and the ability to stage executable hooks. A fix is available in version 1.2.0.post0_14 that adds checks to block unsafe options.

GitPython versions >=0.1.0 and <1.2.0.post0_14 contain a vulnerability in the IndexFile.remove() and Head.checkout() methods. These methods forward arbitrary keyword arguments into git rm and git checkout commands without proper validation. When used with the --pathspec-from-file and --pathspec-file-nul options, this can cause Git to treat the entire contents of a specified file as a single pathspec, leading to the file's contents being leaked in error messages returned by GitPython. This allows an attacker with limited privileges to read arbitrary files on the system through error output.

GitPython versions up to 1.2.0.post0_14 contain a vulnerability in the IndexFile.from_tree, reset, and merge_tree methods where unguarded forwarding of git read-tree options allows an attacker to overwrite arbitrary files with a git-index blob. This occurs because these methods append caller-controlled treeish strings to git read-tree without proper unsafe option checks or a '--' separator, enabling injection of the --index-output option to specify an arbitrary output path. The impact is arbitrary file overwrite at the privileges of the host process, potentially corrupting or destroying files. A fix is available in version 1.2.0.post0_14.

GitPython versions before 3.1.58 contain a path traversal vulnerability due to improper validation of submodule names in .gitmodules files. This flaw allows attackers to create Git repositories at arbitrary filesystem paths outside the intended clone directory by using traversal sequences in submodule names. The vulnerability is rated high severity with a CVSS score of 8.4.

GitPython versions before 3.1.58 contain a config-name injection vulnerability that allows attackers to inject malicious git-config directives by including special characters in option names. This can lead to arbitrary command execution via configuration options like core.sshCommand or core.hooksPath during subsequent git operations.