Getcomposer Composer 1.10.23

CPE Details

Getcomposer Composer 1.10.23
getcomposer
composer
1.10.23
2021-10-07
15h04 +00:00
2021-10-07
15h31 +00:00
CPE NVD
Alerte pour un CPE
Restez informé de toutes modifications pour un CPE spécifique.
Gestion des notifications

CPE Name: cpe:2.3:a:getcomposer:composer:1.10.23:*:*:*:*:*:*:*

Informations

Vendor

getcomposer

Product

composer

Version

1.10.23

Related CVE

Open and find in CVE List

CVE ID Publié Description Score Gravité
CVE-2023-43655 2023-09-29 19h33 +00:00 Composer is a dependency manager for PHP. Users publishing a composer.phar to a public web-accessible server where the composer.phar can be executed as a php file may be subject to a remote code execution vulnerability if PHP also has `register_argc_argv` enabled in php.ini. Versions 2.6.4, 2.2.22 and 1.10.27 patch this vulnerability. Users are advised to upgrade. Users unable to upgrade should make sure `register_argc_argv` is disabled in php.ini, and avoid publishing composer.phar to the web as this is not best practice.
8.8
Haute
CVE-2022-24828 2022-04-13 19h00 +00:00 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.
8.8
Haute