← Back
CVE-2024-35241
Command Injection in CVE-2024-35241 (CVE-2024-35241)
Summary
command injection in CVE-2024-35241 (CVE-2024-35241). Successful exploitation can lead to full system takeover. Exploitable via ``status``.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2024-35241** has been found in CVE-2024-35241.
Attackers can target a specific entry point like ``status`` over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: ?/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "CVE-2024-35241 CVE-2024-35241" on the vendor's site.
CVE-2024-35241 (CVE-2024-35241) — CWE-77 /
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: `status` / `reinstall` / `remove`
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.
❓ What is the problem
**A vulnerability** (CWE-77) exists in CVE-2024-35241. Attackers reach the vulnerable code path via ``status`` without authentication.
📍 Affected scope
CVE-2024-35241 — . Attack surface: `status` / `reinstall` / `remove`.
🔥 Severity
Severity: ?. Successful exploitation can lead to full system takeover
🔧 How to fix
Update to the patched release per vendor advisory.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.依存マニフェストで影響コンポーネントを特定する。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
References
- advisory https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/35xxx/CVE-2024-35241.json
- advisory https://github.com/composer/composer/security/advisories/GHSA-47f6-5gq3-vx9c
- advisory https://nvd.nist.gov/vuln/detail/CVE-2024-35241
- patch https://github.com/composer/composer/commit/b93fc6ca437da35ae73d667d0618749c763b67d4
- patch https://github.com/composer/composer/commit/ee28354ca8d33c15949ad7de2ce6656ba3f68704
- web https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/PO4MU2BC7VR6LMHEX4X7DKGHVFXZV2MC/
- web https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/VLPJHM2WWSYU2F6KHW2BYFGYL4IGTKHC/
- web https://www.vicarius.io/vsociety/posts/cve-2024-35241-detect-composer-vulnerability
- web https://www.vicarius.io/vsociety/posts/cve-2024-35241-mitigate-vulnerable-composer