Логотип exploitDog
Консоль
Логотип exploitDog

exploitDog

suse-cvrf логотип

SUSE-SU-2024:0592-1

Опубликовано: 22 фев. 2024
Источник: suse-cvrf

Описание

Security update for php-composer2

This update for php-composer2 fixes the following issues:

  • CVE-2024-24821: Fixed potential arbitrary code execution when Composer is invoked within a directory with tampered files (bsc#1219757).

Список пакетов

Container bci/php-apache:latest
php-composer2-2.2.3-150400.3.9.1
Container bci/php-fpm:latest
php-composer2-2.2.3-150400.3.9.1
Container bci/php:latest
php-composer2-2.2.3-150400.3.9.1
SUSE Linux Enterprise High Performance Computing 15 SP4-ESPOS
php-composer2-2.2.3-150400.3.9.1
SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
php-composer2-2.2.3-150400.3.9.1
SUSE Linux Enterprise Module for Web and Scripting 15 SP5
php-composer2-2.2.3-150400.3.9.1
SUSE Linux Enterprise Server 15 SP4-LTSS
php-composer2-2.2.3-150400.3.9.1
SUSE Linux Enterprise Server for SAP Applications 15 SP4
php-composer2-2.2.3-150400.3.9.1
SUSE Manager Server 4.3
php-composer2-2.2.3-150400.3.9.1
openSUSE Leap 15.5
php-composer2-2.2.3-150400.3.9.1

Описание

Composer is a dependency Manager for the PHP language. In affected versions several files within the local working directory are included during the invocation of Composer and in the context of the executing user. As such, under certain conditions arbitrary code execution may lead to local privilege escalation, provide lateral user movement or malicious code execution when Composer is invoked within a directory with tampered files. All Composer CLI commands are affected, including composer.phar's self-update. The following scenarios are of high risk: Composer being run with sudo, Pipelines which may execute Composer on untrusted projects, Shared environments with developers who run Composer individually on the same project. This vulnerability has been addressed in versions 2.7.0 and 2.2.23. It is advised that the patched versions are applied at the earliest convenience. Where not possible, the following should be addressed: Remove all sudo composer privileges for all users to mitigate root privilege escalation, and avoid running Composer within an untrusted directory, or if needed, verify that the contents of `vendor/composer/InstalledVersions.php` and `vendor/composer/installed.php` do not include untrusted code. A reset can also be done on these files by the following:```sh rm vendor/composer/installed.php vendor/composer/InstalledVersions.php composer install --no-scripts --no-plugins ```


Затронутые продукты
Container bci/php-apache:latest:php-composer2-2.2.3-150400.3.9.1
Container bci/php-fpm:latest:php-composer2-2.2.3-150400.3.9.1
Container bci/php:latest:php-composer2-2.2.3-150400.3.9.1
SUSE Linux Enterprise High Performance Computing 15 SP4-ESPOS:php-composer2-2.2.3-150400.3.9.1

Ссылки