launch-editor: Improper Neutralization of Special Elements used in a Command
CVE-2024-52011 is a high-severity improper neutralization of special elements used in a command vulnerability in launch-editor from Vitejs, with a CVSS 3.1 base score of 8.3 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, but only if a user takes part, for example by opening a link or file. Affected launch-editor versions: < 2.9.0. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.51% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Check which version of launch-editor you run against the affected versions below, and install the vendor's latest release.
- Read the advisory on github.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
- Because the attack needs a user to take part, warn users about unexpected links and files related to this product until it is patched.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Vitejs | launch-editor | < 2.9.0 | Not stated |
| Vitejs | vite | < 5.4.9 | Not stated |
| Red Hat | Cluster Observability Operator 1.5.0 | Not specified in the record | Not stated |
| Red Hat | Cryostat 4 | Not specified in the record | Not stated |
| Red Hat | Migration Toolkit for Containers | Not specified in the record | Not stated |
| Red Hat | Node HealthCheck Operator | Not specified in the record | Not stated |
| Red Hat | OpenShift Lightspeed | Not specified in the record | Not stated |
| Red Hat | OpenShift Pipelines | Not specified in the record | Not stated |
| Red Hat | OpenShift Service Mesh 2 | Not specified in the record | Not stated |
| Red Hat | OpenShift Service Mesh 3 | Not specified in the record | Not stated |
| Red Hat | Red Hat AMQ Broker 7 | Not specified in the record | Not stated |
| Red Hat | Red Hat Ansible Automation Platform 2 | Not specified in the record | Not stated |
| Red Hat | Red Hat build of Apache Camel - HawtIO 4 | Not specified in the record | Not stated |
| Red Hat | Red Hat Build of Keycloak | Not specified in the record | Not stated |
| Red Hat | Red Hat Build of Podman Desktop | Not specified in the record | Not stated |
| Red Hat | Red Hat Build of Podman Desktop - Tech Preview | Not specified in the record | Not stated |
| Red Hat | Red Hat Data Grid 8 | Not specified in the record | Not stated |
| Red Hat | Red Hat Developer Hub | Not specified in the record | Not stated |
| Red Hat | Red Hat Discovery 2 | Not specified in the record | Not stated |
| Red Hat | Red Hat Enterprise Linux AI (RHEL AI) 3 | Not specified in the record | Not stated |
| Red Hat | Red Hat JBoss Enterprise Application Platform 8 | Not specified in the record | Not stated |
| Red Hat | Red Hat JBoss Enterprise Application Platform Expansion Pack | Not specified in the record | Not stated |
| Red Hat | Red Hat OpenShift AI (RHOAI) | Not specified in the record | Not stated |
| Red Hat | Red Hat OpenShift Container Platform 4 | Not specified in the record | Not stated |
| Red Hat | Red Hat OpenShift Dev Spaces | Not specified in the record | Not stated |
Version data comes from the organisation that assigned the CVE; 3 further products are omitted here. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- RequiredA user must take an action such as opening a file or link.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- LowPerformance or availability is reduced.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:L. Scored by CNA.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 4.0 | 7.5 | High | CNA (github.com) |
| CVSS 3.1 | 8.3 | High | CNA |
Official description
launch-editor allows users to open files with line numbers in editor from Node.js. Prior to version 2.9.0, 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. This issue has been fixed in the `launch-editor` version 2.9.0, corresponding to vite version 5.4.9.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Neutralization of Special Elements used in a Command
The product constructs all or part of a command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended command when it is sent to a downstream component.
How developers prevent this class of flaw
- If at all possible, use library calls rather than external processes to recreate the desired functionality.
- If possible, ensure that all external commands called from the program are statically created.
- Run time: Run time policy enforcement may be used in an allowlist fashion to prevent use of any non-sanctioned commands.
More Improper Neutralization of Special Elements used in a Command vulnerabilities (CWE-77)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
Other references
Other vulnerabilities in launch-editor
- 7.5 High severity
Recent Improper Neutralization of Special Elements used in a Command vulnerabilities
- 7.3 High severity
- 7.3 High severity
- 7.3 High severity
- 9.9 Critical severity
- 8.8 High severity
- 9.8 Critical severity
Spotted an error? Tell us.