Getcomposer Composer

Command injection in composer on Windows

Missing argument delimiter can lead to code execution via VCS repository URLs or source download URLs on systems with Mercurial in composer

Composer has Command Injection via Malicious Perforce Reference

Missing input validation can lead to command execution in composer

Remote Code Execution via web-accessible composer.phar

Composer before 2016-02-10 allows cache poisoning from other projects built on the same host. This results in attacker-controlled code entering a server-side build process. The issue occurs because of the way that dist packages are cached. The cache key is derived from the package name, the dist type, and certain other data from the package repository (which may simply be a commit hash, and thus can be found by an attacker). Versions through 1.0.0-alpha11 are affected, and 1.0.0 is unaffected.

Code execution and possible privilege escalation via compromised InstalledVersions.php or installed.php in Composer

Composer is vulnerable to Command Injection via Malicious Perforce Repository

Composer vulnerable to ANSI sequence injection