composer/composer
Affected
- introduced
0, fixed1.10.26(ecosystem)
Fixed versions
1.10.26
Fix
The export has no generic command for this ecosystem.
Advisory
Also known as: BIT-composer-2022-24828, CVE-2022-24828
Missing input validation can lead to command execution in composer
The Composer method VcsDriver::getFileContent() with user-controlled $file or $identifier arguments is susceptible to an argument injection vulnerability. It can be leveraged to gain arbitrary command execution if the Mercurial or the Git driver are used.
This led to a vulnerability on Packagist.org and Private Packagist, i.e., using the composer.json readme field as a vector for injecting parameters into the $file argument for the Mercurial driver or via the $identifier argument for the Git and Mercurial drivers.
Composer itself can be attacked through branch names by anyone controlling a Git or Mercurial repository, which is explicitly listed by URL in a project's composer.json.
To the best of our knowledge, this was not actively exploited. The vulnerability has been patched on Packagist.org and Private Packagist within a day of the vulnerability report.
High Basis: The source's own band: HIGH
0, fixed 1.10.26 (ecosystem)1.10.26
The export has no generic command for this ecosystem.
2.0, fixed 2.2.12 (ecosystem)2.2.12
The export has no generic command for this ecosystem.
2.3, fixed 2.3.5 (ecosystem)2.3.5
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