When installing a package from a Mercurial VCS URL (ie pip install hg+…) with pip prior to v23.3, the specified Mercurial revision could be used to inject arbitrary configuration options to the hg clone call (ie –config). Controlling the Mercurial configuration can modify how and which repository is installed. This vulnerability does not affect users who arent installing from Mercurial.
The product constructs all or part of a command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended command when it is sent to a downstream component.
Name | Vendor | Start Version | End Version |
---|---|---|---|
Pip | Pypa | * | 23.3 (excluding) |
Red Hat Ansible Automation Platform 2.4 for RHEL 8 | RedHat | automation-controller-0:4.5.7-1.el8ap | * |
Red Hat Ansible Automation Platform 2.4 for RHEL 9 | RedHat | automation-controller-0:4.5.7-1.el9ap | * |
Python-pip | Ubuntu | bionic | * |
Python-pip | Ubuntu | lunar | * |
Python-pip | Ubuntu | mantic | * |
Python-pip | Ubuntu | trusty | * |
Python-pip | Ubuntu | trusty/esm | * |
Python-pip | Ubuntu | xenial | * |
Command injection vulnerabilities typically occur when:
Many protocols and products have their own custom command language. While OS or shell command strings are frequently discovered and targeted, developers may not realize that these other command languages might also be vulnerable to attacks. Command injection is a common problem with wrapper programs.