CyberRota Analysis
AI-GeneratedComposer versions 1.0 through 2.2.30 and 2.10.3 are vulnerable to a command injection flaw that allows a malicious dependency package to execute arbitrary commands via the Perforce p4 client when installed from untrusted sources. This could lead to unauthorized command execution with the privileges of the user or CI account, posing a significant security risk. Organizations using affected versions of Composer, particularly those in CI/CD environments, should prioritize upgrading to the patched versions to mitigate this vulnerability.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
Composer is a dependency Manager for the PHP language. From 1.0 until 2.2.30 and 2.10.3, a malicious dependency package from a custom Composer repository or an untrusted composer.lock file could set source.type to perforce and source.url to an rsh: or jsh: P4PORT value. When the Perforce p4 client was installed and Composer installed the package from source through composer install or composer update, including --prefer-source, Composer\Util\Perforce passed the address to p4 without validation, causing p4 to run a local command with the privileges of the user or CI account. Packagist.org does not permit Perforce source metadata. This issue is fixed in versions 2.2.30 and 2.10.3.