Sign in Sign up
JA · EN · FR
SecPulse
Categories
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.

Original description

The description as published by the source.

Summary

Due to the insufficient sanitization of the file argument in the launchEditor, an attacker can execute arbitrary commands on Windows by supplying a filename that contains special characters.

Impact

If the following conditions are met, an attacker can execute arbitrary commands on the computer that is using the launch-editor:

  • An attacker can place a file with the malicious filename
  • An attacker can call the launchEditor method with the file argument controlled
  • The launch-editor package is running on Windows

For example, some development server using this package satisfy these conditions, as a malicious website might be able to force the downloading of a file and the path of that file is predictable.

Patch

This issue has been fixed in the launch-editor version 2.9.0 (commit).

Source: NIST National Vulnerability Database NVD GitHub Advisory

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-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

Check the vendor advisory for the affected versions of 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

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. 2
    Apply patch patch 
    Upgrade launch-editor to 2.9.0

    ステージング環境で 2.9.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

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

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

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

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details