composer/composer
Affected
- introduced
2.0.0-alpha1, fixed2.2.23(ecosystem)
Fixed versions
2.2.23
Fix
The export has no generic command for this ecosystem.
Advisory
Also known as: BIT-composer-2024-24821, CVE-2024-24821
Composer code execution and possible privilege escalation via compromised InstalledVersions.php or installed.php
Impact
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 are of high risk:
Patches
2.7.0, 2.2.23
Workarounds
Where not possible, the following should be addressed:
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:
rm vendor/composer/installed.php vendor/composer/InstalledVersions.php
composer install --no-scripts --no-pluginsHigh Basis: The source's own band: HIGH
2.0.0-alpha1, fixed 2.2.23 (ecosystem)2.2.23
The export has no generic command for this ecosystem.
2.3.0-rc1, fixed 2.7.0 (ecosystem)2.7.0
The export has no generic command for this ecosystem.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0