Remote code execution via trusted notebook command URIs
Published Oct 11, 2022 · Updated Jan 2, 2025
Remote code execution in Microsoft Visual Studio Code before 1.72.1 allows remote attackers to run commands through a malicious notebook. A payload URL opens a remote notebook as trusted, letting injected HTML activate a command URI whose terminal options select an attacker-supplied executable. A user must follow a crafted link or visit an attacker-controlled site; commands run with the user's privileges and can reach connected Remote Development hosts.
Summary
What happened
Remote code execution in Microsoft Visual Studio Code before 1.72.1 allows remote attackers to run commands through a malicious notebook. A payload URL opens a remote notebook as trusted, letting injected HTML activate a command URI whose terminal options select an attacker-supplied executable. A user must follow a crafted link or visit an attacker-controlled site; commands run with the user's privileges and can reach connected Remote Development hosts.
The record
- CVE
- CVE-2022-41034
- Published
- Oct 11, 2022
- Updated
- Jan 2, 2025
- Vendor
- Microsoft
- Product
- Visual Studio Code
- Classifications
- T1204.001
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 11, 2022CVE publishedPublication date reported by the CVE source.
- Jan 2, 2025Record 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=1.0.0 <1.72.1
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
- Google Security Research malicious-notebook proof of conceptproof of concept · demonstrated
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