launch-editor path check bypass in Windows file arguments
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, launch-editor-middleware processes an attacker-controlled Windows file argument where the file argument ends in a parent-directory component plus a line-and-column suffix: the path is resolved while the suffix is still present, and launch-editor removes the suffix before its existsSync check, leaving the existing parent directory for existsSync and allowing the attacker-controlled file argument to pass filename existence validation without requiring the malicious filename to exist. The bypass can lead to OS command injection when combined with the separately described Windows percent-expansion flaw. This issue is fixed in version 2.14.2.
From the CVE record · GitHub_M
On Windows, launch-editor-middleware can accept an attacker-controlled file argument that bypasses filename existence validation. Combined with a separately described Windows percent-expansion flaw, this can lead to OS command injection; the input does not specify authentication or user-interaction requirements.
Check installations of npm launch-editor below 2.14.2, vite in the listed affected ranges (below 6.4.4, 7.0.0–7.3.6, 8.0.0–8.1.5, 8.2.0–8.2.3, or 8.3.0–8.3.2), and vite-plus below 1.1.0.