launch-editor editor option injection via crafted filenames
vitejs launch-editor · vitejs vite · vitejs vite-plus
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| launch-editor npm |
|
|
| vite npm |
|
vitejs launch-editor · vitejs vite · vitejs vite-plus
| Product | Affected | Fixed in |
|---|---|---|
| launch-editor npm |
|
|
| vite npm |
|
|
| vite-plus npm |
|
|
launch-editor allows users to open files with line numbers in editor from Node.js. Prior to 2.14.2, when an attacker can create a filesystem entry beginning with plus or minus in the working directory, an affected editor is selected, and the path can remain relative or is converted to a relative WSL path, launchEditor forwards the path without forcing it to be interpreted as a positional filename. Editor option parsing then treats the attacker-controlled filename as a command-line flag, which can cause unintended file overwrite or arbitrary command execution by the selected editor. The affected editors are Vim and gVim, MacVim, Emacs and Emacsclient, and Notepad++ when a plugin exposes dangerous operations; WSL path conversion keeps Vite and newer middleware callers exposed. This issue is fixed in version 2.14.2.
From the CVE record · GitHub_M
launch-editor can pass an attacker-controlled filename beginning with + or - to an affected editor as a command-line option. If an attacker can create such a filesystem entry in the working directory, an affected editor is selected, and the path remains relative or becomes a relative WSL path, this can cause unintended file overwrite or arbitrary command execution. The issue also affects Vite and vite-plus callers.
Check installations of npm launch-editor before 2.14.2, vite before 6.4.4 or in the affected 7.x and 8.x ranges, and vite-plus before 1.1.0.