Loading vulnerability…
CVE-2024-52011 is a command injection vulnerability in the Node.js package launch-editor. In versions prior to 2.9.0, the launchEditor functionality insufficiently sanitizes the file argument before invoking the editor on Windows. If an attacker can influence the filename supplied to launchEditor, and that filename contains shell-special characters, those characters can be interpreted in a way that results in arbitrary command execution. The issue affects Windows environments and was fixed in launch-editor 2.9.0. The corresponding fix is included for users of Vite in version 5.4.9.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
launch-editor. This can allow an attacker to run system commands, compromise developer workstations or other affected systems, access or modify local data, install additional tooling or malware, and potentially use the host as a pivot for further activity.If you can’t patch tonight, do this now.
launchEditor, especially on Windows. Prevent attackers from creating or influencing filenames containing shell-special characters in workflows that invoke launch-editor. Restrict use of the affected functionality to trusted inputs and environments until the package can be upgraded.Patch, then assume compromise.
launch-editor to version 2.9.0 or later. If the vulnerable package is consumed through Vite, upgrade Vite to version 5.4.9 or later, which includes the corresponding fix. Validate that no older vulnerable versions remain pinned in lockfiles or transitive dependency trees.No valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
2 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.