Git before 2.19.2 on Linux and UNIX executes commands from the current working directory (as if . were at the end of $PATH) in certain cases involving the run_command() API and run-command.c, because there was a dangerous change from execvp to execv during 2017.
The product searches for critical resources using an externally-supplied search path that can point to resources that are not under the product’s direct control.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Git | Git-scm | * | 2.19.2 (excluding) |
| Red Hat Software Collections for Red Hat Enterprise Linux 7 | RedHat | rh-git218-git-0:2.18.1-3.el7 | * |
| Red Hat Software Collections for Red Hat Enterprise Linux 7.4 EUS | RedHat | rh-git218-git-0:2.18.1-3.el7 | * |
| Red Hat Software Collections for Red Hat Enterprise Linux 7.5 EUS | RedHat | rh-git218-git-0:2.18.1-3.el7 | * |
| Red Hat Software Collections for Red Hat Enterprise Linux 7.6 EUS | RedHat | rh-git218-git-0:2.18.1-3.el7 | * |
| Git | Ubuntu | bionic | * |
| Git | Ubuntu | cosmic | * |
| Git | Ubuntu | devel | * |
| Git | Ubuntu | upstream | * |
This might allow attackers to execute their own programs, access unauthorized data files, or modify configuration in unexpected ways. If the product uses a search path to locate critical resources such as programs, then an attacker could modify that search path to point to a malicious program, which the targeted product would then execute. The problem extends to any type of critical resource that the product trusts. Some of the most common variants of untrusted search path are: