| Package | Affected versions | Patched versions |
|---|---|---|
| gitpython | < 3.1.33 | 3.1.33 |
| gitpython | ≤ 3.1.32 |
When resolving a program, Python/Windows look for the current working directory, and after that the PATH environment (see big warning in https://docs.python.org/3/library/subprocess.html#popen-constructor). GitPython defaults to use the git command, if a user runs GitPython from a repo has a git.exe or git executable, that program will be run instead of the one in the user's PATH.
This is more of a problem on how Python interacts with Windows systems, Linux and any other OS aren't affected by this. But probably people using GitPython usually run it from the CWD of a repo.
The execution of the git command happens in
And there are other commands executed that should probably be aware of this problem.
On a Windows system, create a git.exe or git executable in any directory, and import or run GitPython from that directory
python -c "import git"
The git executable from the current directory will be run.
An attacker can trick a user to download a repository with a malicious git executable, if the user runs/imports GitPython from that directory, it allows the attacker to run any arbitrary commands.
C:\\Program Files\\Git\\cmd\\git.EXE (default git path installation).GIT_PYTHON_GIT_EXECUTABLE environment variable on Windows systems.GIT_PYTHON_GIT_EXECUTABLE env var to an absolute path.PATH environment variable (suggested by @Byron)[!NOTE] This vulnerability was reported via email, and it was decided to publish it here and make it public, so the community is aware of it, and a fix can be provided.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free