Composer is vulnerable to Command Injection via Malicious Perforce Repository
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in composer/composer 2.2.27 and composer/composer 2.9.6.
Composer is a dependency manager for PHP. Versions 1.0 through 2.2.26 and 2.3 through 2.9.5 contain a command injection vulnerability in the Perforce::generateP4Command() method, which constructs shell commands by interpolating user-supplied Perforce connection parameters (port, user, client) without proper escaping. An attacker can inject arbitrary commands through these values in a malicious composer.json declaring a Perforce VCS repository, leading to command execution in the context of the user running Composer, even if Perforce is not installed. VCS repositories are only loaded from the root composer.json or the composer config directory, so this cannot be exploited through composer.json files of packages installed as dependencies. Users are at risk if they run Composer commands on untrusted projects with attacker-supplied composer.json files. This issue has been fixed in Composer 2.2.27 (2.2 LTS) and 2.9.6 (mainline).
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| composer | >=1.0 <2.2.27, >=2.3 <2.9.6 | ||
| getcomposer | composer | >=1.0.0 <=2.2.26, >=2.3.0 <=2.9.5 | |
| packagist: composer/composer | >=1.0.0 <2.2.27, >=2.3.0 <2.9.6 | 2.2.27, 2.9.6 |
Timeline
Every event on this vulnerability
Embed
A live severity badge for an advisory, README or ticket