Multiple vulnerabilities have been discovered in Composer, the worst of which can lead to arbitrary code execution.
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`.
[ 1 ] CVE-2022-24828
https://nvd.nist.gov/vuln/detail/CVE-2022-24828
[ 2 ] CVE-2023-43655
https://nvd.nist.gov/vuln/detail/CVE-2023-43655
This GLSA and any updates to it are available for viewing at
the Gentoo Security Website:
https://security.gentoo.org/glsa/202508-06
style>.gentoo_availability{display:block;}
Security is a primary focus of Gentoo Linux and ensuring the
confidentiality and security of our users' machines is of utmost
importance to us. Any security concerns should be addressed to
security@gentoo.org or alternatively, you may file a bug at
https://bugs.gentoo.org.
Get the latest Linux and open source security news straight to your inbox.
There is no known workaround at this time.