NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · Composer (PHP)

CVE-2024-24821: Composer code execution and possible privilege escalation via compromised InstalledVersions.php or installed.php

highCVSS 3.1 8.8GHSA-7c6p-848j-wh5h

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.

Published Feb 8, 2024 · Updated Feb 9, 2024

Affected packages

composer/composer

Ecosystem
Composer (PHP)
Affected
>= 2.0.0-alpha1, < 2.2.23
Fixed in
2.2.23
Check
composer show composer/composer

composer/composer

Ecosystem
Composer (PHP)
Affected
>= 2.3.0-rc1, < 2.7.0
Fixed in
2.7.0
Check
composer show composer/composer

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

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:

  • 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.

Patches

2.7.0, 2.2.23

Workarounds

  • 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.
  • 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:

rm vendor/composer/installed.php vendor/composer/InstalledVersions.php
composer install --no-scripts --no-plugins

Credited to edonsec.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology

More Composer (PHP) vulnerabilities

All Composer (PHP) entries