GHSA-wg36-wvj6-r67p Composer has a command injection via malicious perforce repository

• Packagist composer/composer: >= 2.3.0, < 2.9.6 → fixed in 2.9.6 • Packagist composer/composer: >= 1.0.0, < 2.2.27 → fixed in 2.2.27

Impact The `Perforce::generateP4Command()` method constructed shell commands by interpolating user-supplied Perforce connection parameters (port, user, client) without proper escaping. An attacker controlling a repository configuration in a malicious composer.json declaring a Perforce VCS repository could inject arbitrary commands through these values, leading to command execution in the context of the user running Composer. Composer would execute these injected commands even if Perforce is not installed. VCS repositories are only loaded from the root composer.json file located in the directory you execute Composer commands in and from the composer config directory (e.g. `~/.config/composer/composer.json`). So this vulnerability cannot be exploited through composer.json files of packages installed as dependencies. You are at risk of command execution if you run Composer commands on untrusted projects with attacker supplied composer.json files, regardless of whether you or any of your dependencies use Perforce. Patches Fixed in Composer 2.2.27 (2.2 LTS) and 2.9.6 (mainline) Workarounds • Carefully inspect composer.json files before running Composer on them. Verify that Perforce-related fields contain valid values. • Only run Composer commands on projects from trusted sources.