Staging Environment: Content and features may be unstable or change without notice.
Search for packages
Package details: pkg:composer/composer/composer@1.0.0-alpha11
purl pkg:composer/composer/composer@1.0.0-alpha11
Next non-vulnerable version 1.10.28
Latest non-vulnerable version 2.10.0-RC1
Risk 4.0
Vulnerabilities affecting this package (5)
Vulnerability Summary Fixed by
VCID-116y-np6h-e7f7
Aliases:
CVE-2015-8371
GHSA-725m-w832-q973
Cache Poisoning composer is vulnerable to Cache Injection.
1.0.0-alpha2
Affected by 4 other vulnerabilities.
1.0.0
Affected by 7 other vulnerabilities.
VCID-5ccv-kq34-9kf2
Aliases:
CVE-2021-41116
GHSA-frqg-7g38-6gcf
arbitrary command execution
1.10.23
Affected by 4 other vulnerabilities.
2.0.0-RC1
Affected by 2 other vulnerabilities.
2.1.9
Affected by 8 other vulnerabilities.
VCID-8zzn-tauw-mydc
Aliases:
CVE-2022-24828
GHSA-x7cr-6qr6-2hh6
Improper Input Validation Composer is a dependency manager for the PHP programming language. Integrators using Composer code to call `VcsDriver::getFileContent` can have a code injection vulnerability if the user can control the `$file` or `$identifier` argument. This leads to a vulnerability on packagist.org for example where the composer.json's `readme` field can be used as a vector for injecting parameters into hg/Mercurial via the `$file` argument, or git via the `$identifier` argument if you allow arbitrary data there (Packagist does not, but maybe other integrators do). Composer itself should not be affected by the vulnerability as it does not call `getFileContent` with arbitrary data into `$file`/`$identifier`. To the best of our knowledge this was not abused, and the vulnerability has been patched on packagist.org and Private Packagist within a day of the vulnerability report.
1.10.26
Affected by 3 other vulnerabilities.
2.2.12
Affected by 7 other vulnerabilities.
2.3.5
Affected by 7 other vulnerabilities.
VCID-bfsn-ds7s-j3ha
Aliases:
CVE-2023-43655
GHSA-jm6m-4632-36hf
Composer Remote Code Execution vulnerability via web-accessible composer.phar Users publishing a composer.phar to a public web-accessible server where the composer.phar can be executed as a php file may be impacted if PHP also has `register_argc_argv` enabled in php.ini.
1.10.27
Affected by 2 other vulnerabilities.
2.0.0-RC1
Affected by 2 other vulnerabilities.
2.2.22
Affected by 6 other vulnerabilities.
2.3.0-RC1
Affected by 0 other vulnerabilities.
2.6.4
Affected by 6 other vulnerabilities.
VCID-m72z-wq6e-6qg3
Aliases:
CVE-2021-29472
GHSA-h5h8-pc6h-jvvx
Improper Neutralization of Argument Delimiters in a Command ('Argument Injection') Composer is a dependency manager for PHP. URLs for Mercurial repositories in the root composer.json and package source download URLs are not sanitized correctly. Specifically crafted URL values allow code to be executed in the HgDriver if hg/Mercurial is installed on the system. The impact to Composer users directly is limited as the composer.json file is typically under their own control and source download URLs can only be supplied by third party Composer repositories they explicitly trust to download and execute source code from, e.g. Composer plugins. The main impact is to services passing user input to Composer, including Packagist.org and Private Packagist. This allowed users to trigger remote code execution. The vulnerability has been patched on Packagist.org and Private Packagist within 12h of receiving the initial vulnerability report and based on a review of logs, to the best of our knowledge, was not abused by anyone. Other services/tools using VcsRepository/VcsDriver or derivatives may also be vulnerable and should upgrade their composer/composer dependency immediately. Versions 1.10.22 and 2.0.13 include patches for this issue.
1.10.22
Affected by 5 other vulnerabilities.
2.0.13
Affected by 9 other vulnerabilities.
Vulnerabilities fixed by this package (0)
Vulnerability Summary Aliases
This package is not known to fix vulnerabilities.