Unauthenticated remote code execution
Published Dec 15, 2021 · Updated Aug 4, 2024
Remote code execution in Microsoft Visual Studio Code WSL before 0.63.11 allows remote attackers to execute code through its WSL server. Microsoft identifies the vulnerable locus as the VS Code server running inside the WSL distribution but does not disclose the unsafe operation on network input. No authentication or user interaction is required, and successful exploitation grants code execution with the server process's access.
Summary
What happened
Remote code execution in Microsoft Visual Studio Code WSL before 0.63.11 allows remote attackers to execute code through its WSL server. Microsoft identifies the vulnerable locus as the VS Code server running inside the WSL distribution but does not disclose the unsafe operation on network input. No authentication or user interaction is required, and successful exploitation grants code execution with the server process's access.
The record
- CVE
- CVE-2021-43907
- Published
- Dec 15, 2021
- Updated
- Aug 4, 2024
- Vendor
- Microsoft
- Product
- Visual Studio Code WSL
- Classifications
- T1210
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 15, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <0.63.11
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo