CVE-2024-52011

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.

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.

Untrusted input is inserted into a command that is later executed by the application, allowing the attacker to alter the intent of that command. Typical impact: arbitrary command execution in the application's environment.

Kodem intelligence

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

1. What is CVE-2024-52011? CVE-2024-52011 is a high-severity command injection vulnerability in launch-editor (npm), affecting versions <= 2.8.2. It is fixed in 2.9.0, 5.4.9. Untrusted input is inserted into a command that is later executed by the application, allowing the attacker to alter the intent of that command.
2. Which packages are affected by CVE-2024-52011?
   • launch-editor (npm) (versions <= 2.8.2)
   • vite (npm) (versions <= 5.4.8)
3. Is there a fix for CVE-2024-52011? Yes. CVE-2024-52011 is fixed in 2.9.0, 5.4.9. Upgrade to this version or later.
4. Is CVE-2024-52011 exploitable, and should I be worried? Whether CVE-2024-52011 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
5. What actually determines whether CVE-2024-52011 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
6. How do I fix CVE-2024-52011?
   • Upgrade launch-editor to 2.9.0 or later
   • Upgrade vite to 5.4.9 or later