Command Injection in composer/composer (CVE-2021-41116)
Summary
Command injection in composer/composer (CVE-2021-41116). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 2.1.9 or later.
Original description
The description as published by the source.
Composer is an open source dependency manager for the PHP language. In affected versions windows users running Composer to install untrusted dependencies are subject to command injection and should upgrade their composer version. Other OSs and WSL are not affected. The issue has been resolved in composer versions 1.10.23 and 2.1.9. There are no workarounds 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-41116 has been found in composer/composer.
Successful exploitation can lead to full system takeover.
What to do: upgrade composer/composer to 2.1.9 or later.
If unsure, ask your IT team or search "composer/composer CVE-2021-41116" on the vendor's site.
CVE-2021-41116 (composer/composer) — CWE-77
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 2.1.9 — 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-77) 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.1.9.
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.1.9ステージング環境で 2.1.9 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- patch github.com
- web github.com
- web sonarsource.com
- web tenable.com
- web sonarsource.com