Vulnerability in composer/composer (CVE-2021-29472)
Summary
Vulnerability in composer/composer (CVE-2021-29472). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 2.0.13 or later.
Original description
The description as published by the source.
Composer is a dependency manager for PHP. URLs for Mercurial repositories in the root composer.json and package source download URLs are not sanitized correctly. Specifically crafted URL values allow code to be executed in the HgDriver if hg/Mercurial is installed on the system. The impact to Composer users directly is limited as the composer.json file is typically under their own control and source download URLs can only be supplied by third party Composer repositories they explicitly trust to download and execute source code from, e.g. Composer plugins. The main impact is to services passing user input to Composer, including Packagist.org and Private Packagist. This allowed users to trigger remote code execution. The vulnerability has been patched on Packagist.org and Private Packagist within 12h of receiving the initial vulnerability report and based on a review of logs, to the best of our knowledge, was not abused by anyone. Other services/tools using VcsRepository/VcsDriver or derivatives may also be vulnerable and should upgrade their composer/composer dependency immediately. Versions 1.10.22 and 2.0.13 include patches for this issue.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2021-29472 has been found in composer/composer.
Successful exploitation can lead to full system takeover.
What to do: upgrade composer/composer to 2.0.13 or later.
If unsure, ask your IT team or search "composer/composer CVE-2021-29472" on the vendor's site.
CVE-2021-29472 (composer/composer) — CWE-88
Attack vector: remote (network-reachable) / no user interaction
Patched: 2.0.13 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-88) exists in composer/composer.
Check the vendor advisory for the affected versions of composer/composer.
Severity: ?. Successful exploitation can lead to full system takeover.
Update to 2.0.13.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'composer/composer' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'composer/composer' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
composer/composerを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade composer/composer to 2.0.13ステージング環境で 2.0.13 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2021-29472 composer Fixed in: 2.0.9-2
References
- advisory github.com
- advisory lists.debian.org
- advisory debian.org
- advisory getcomposer.org
- advisory blog.sonarsource.com
- package github.com
- web nvd.nist.gov
- web blog.sonarsource.com
- web getcomposer.org
- web github.com
- web lists.fedoraproject.org
- web lists.fedoraproject.org
- web lists.fedoraproject.org
- web lists.fedoraproject.org