CVE-2022-24828: Missing input validation can lead to command execution in composer

Published Apr 13, 2022
·
Updated

Composer is a dependency manager for the PHP programming language. 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. To the best of our knowledge this was not abused, and the vulnerability has been patched on packagist.org and Private Packagist within a day of the vulnerability report.

Other sources

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.

GitHub

Affected Software

11 affected componentsFixes available
composer/composer/composer>=2.3, <2.3.5, >=2.0, <2.2.12, <1.10.26
composer/composer/composer>=2.3<2.3.5
2.3.5
composer/composer/composer>=2.0<2.2.12
2.2.12
composer/composer/composer<1.10.26
1.10.26
Getcomposer Composer<1.10.26
Getcomposer Composer>=2.0.0<2.2.12
Getcomposer Composer>=2.3.0<2.3.5
Tenable Tenable.Sc<5.21.0
Fedoraproject Fedora=34
Fedoraproject Fedora=35
Fedoraproject Fedora=36

Event History

Apr 13, 2022
Advisory Published
02:54 PM
CVE Published
via MITRE·09:00 PM
Data Sourced
via MITRE·09:00 PM
DescriptionSeverityWeakness
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is CVE-2022-24828?

CVE-2022-24828 is a vulnerability in the Composer dependency manager for PHP that allows command execution due to missing input validation.

2

How does CVE-2022-24828 affect Composer?

CVE-2022-24828 affects Composer versions up to 2.3.5, 2.2.12, and 1.10.26.

3

What is the severity of CVE-2022-24828?

The severity of CVE-2022-24828 is high with a CVSS score of 8.8.

4

How can I fix CVE-2022-24828?

To fix CVE-2022-24828, upgrade to Composer version 2.3.6, 2.2.13, or 1.10.27.

5

Where can I find more information about CVE-2022-24828?

You can find more information about CVE-2022-24828 at the following references: [Link 1], [Link 2], [Link 3].

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203