# CVE-2022-24828: Missing input validation can lead to command execution in composer > Attackers can execute arbitrary commands via crafted input in VcsDriver::getFileContent when integrators allow user-controlled file or identifier arguments. - **Severity:** High 8.3 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 13 Apr 2022 - **Updated:** 23 Apr 2025 - **Also known as:** BIT-composer-2022-24828, CLEANSTART-2024-VD23894, DEBIAN-CVE-2022-24828, GHSA-x7cr-6qr6-2hh6, SUSE-SU-2022:3020-1, UBUNTU-CVE-2022-24828, openSUSE-SU-2024:12048-1, openSUSE-SU-2024:12054-1 ## What is CVE-2022-24828? CVE-2022-24828 is a high-severity command injection vulnerability in Fedoraproject Fedora, published on 13 Apr 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. ### Official description 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. Weakness: CWE-88 (Improper Neutralization of Argument Delimiters in a Command), CWE-20 (Improper Input Validation) ## Which versions are affected by CVE-2022-24828? 7 open source packages ship an affected version, including composer/composer and composer. It affects 3 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `composer/composer` | Packagist | All versions | 1.10.26 | | `composer/composer` | Packagist | All versions | 1.10.26 | | `composer/composer` | Packagist | From 2.0 | 2.2.12 | | `composer/composer` | Packagist | From 2.0 | 2.2.12 | | `composer/composer` | Packagist | From 2.3 | 2.3.5 | | `composer/composer` | Packagist | From 2.3 | 2.3.5 | | `composer` | Bitnami | All versions | 1.10.26, 2.2.12, 2.3.5 | | `php-composer2` | SUSE:Linux Enterprise Module for Web and Scripting 15 SP4 | All versions | 2.2.3-150400.3.3.1 | | `php-composer2` | openSUSE:Leap 15.4 | All versions | 2.2.3-150400.3.3.1 | | `php-composer` | openSUSE:Tumbleweed | All versions | 1.10.26-1.1 | | `php-composer2` | openSUSE:Tumbleweed | All versions | 2.3.5-1.1 | Products: Fedoraproject Fedora, Getcomposer Composer, Tenable Tenable.sc. ## How do I fix CVE-2022-24828? Upgrade composer/composer to a fixed version for your release line: 1.10.26, 2.2.12 or 2.3.5. ## Is CVE-2022-24828 being exploited? There is no known exploitation of CVE-2022-24828 in the wild and no public exploit code. ## Other vulnerabilities in Fedoraproject Fedora - [CVE-2024-4577](https://insights.sbomify.com/CVE-2024-4577/): PHP-CGI OS Command Injection (critical 9.8, exploited in the wild) - [CVE-2021-39226](https://insights.sbomify.com/CVE-2021-39226/): Grafana Authentication Bypass (critical 9.8, exploited in the wild) - [CVE-2019-5544](https://insights.sbomify.com/CVE-2019-5544/): VMware ESXi and Horizon DaaS OpenSLP Heap-Based Buffer Overflow (critical 9.8, exploited in the wild) - [CVE-2024-4947](https://insights.sbomify.com/CVE-2024-4947/): Google Chromium V8 Type Confusion (critical 9.6, exploited in the wild) - [CVE-2024-4671](https://insights.sbomify.com/CVE-2024-4671/): Google Chromium Visuals Use-After-Free (critical 9.6, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2022-24828 and fix it if it is affected. What it is: CVE-2022-24828 is a high-severity command injection vulnerability in Fedoraproject Fedora, published on 13 Apr 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2022-24828 in the wild and no public exploit code. Affected packages and fixed versions: - composer/composer (Packagist): affected all versions; fixed in 1.10.26 - composer/composer (Packagist): affected all versions; fixed in 1.10.26 - composer/composer (Packagist): affected from 2.0; fixed in 2.2.12 - composer/composer (Packagist): affected from 2.0; fixed in 2.2.12 - composer/composer (Packagist): affected from 2.3; fixed in 2.3.5 - composer/composer (Packagist): affected from 2.3; fixed in 2.3.5 - composer (Bitnami): affected all versions; fixed in 1.10.26, 2.2.12, 2.3.5 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2022-24828/ (Markdown: https://insights.sbomify.com/CVE-2022-24828/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2022-24828 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-24828 - OSV: https://osv.dev/vulnerability/CVE-2022-24828 --- From sbomify Insights: https://insights.sbomify.com/CVE-2022-24828/ Summaries are generated and may contain mistakes; the official description above is the record.