Sign in Sign up
JA · EN · FR
SecPulse
← Back
CVE-2024-52011 high CVSS 8.3

Command Injection in launch-editor (CVE-2024-52011)

Summary

command injection in launch-editor (CVE-2024-52011). Confidential information can be exposed externally. Exploitable via ``file``. Mitigation: upgrade to `2.9.0` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **CVE-2024-52011** has been found in launch-editor. Attackers can target a specific entry point like ``file`` over the network to misuse the product. Confidential information can be exposed externally. CVSS score: 8.3/10. What to do: upgrade launch-editor to **2.9.0** or later. If unsure, ask your IT team or search "launch-editor CVE-2024-52011" on the vendor's site.
CVE-2024-52011 (launch-editor) — CWE-77 / CVSS v3 8.3 Attack vector: remote (network-reachable) / unauthenticated Attack surface: `file` / `launchEditor` Patched: `2.9.0` — 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.
❓ What is the problem
**A vulnerability** (CWE-77) exists in launch-editor. Attackers reach the vulnerable code path via ``file`` without authentication.
📍 Affected scope
launch-editor — . Attack surface: `file` / `launchEditor`.
🔥 Severity
Severity: High (CVSS 8.3/10). Confidential information can be exposed externally
🔧 How to fix
Update to **2.9.0**.
🛡️ 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. Run `grep -r 'launch-editor' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response Actions (7 steps)

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'launch-editor' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `launch-editor` を grep し、稼働しているサービス・バージョンを把握する。

  2. 6
    Apply patch patch 
    Upgrade launch-editor to 2.9.0

    ステージング環境で 2.9.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。

  3. 7
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

npm launch-editor
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"2.9.0"}]}]
npm vite
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"5.4.9"}]}]

References

🍪 About cookies

We use cookies to keep you logged in, remember your language, and improve the service.

Details →