Privilege escalation via out-of-workspace binary resolution
Published Feb 11, 2025 · Updated Feb 26, 2026
Improper access control in Microsoft Visual Studio Code JavaScript Debugger before 1.97.1 allows local users to execute a planted binary. NodeBinaryProvider walks upward from the debug working directory and accepts an executable from a parent node_modules/.bin directory outside the workspace. A local user must modify a commonly searched directory and induce the victim to start JavaScript debugging, causing the binary to run with the victim's privileges.
Summary
What happened
Improper access control in Microsoft Visual Studio Code JavaScript Debugger before 1.97.1 allows local users to execute a planted binary. NodeBinaryProvider walks upward from the debug working directory and accepts an executable from a parent node_modules/.bin directory outside the workspace. A local user must modify a commonly searched directory and induce the victim to start JavaScript debugging, causing the binary to run with the victim's privileges.
The record
- CVE
- CVE-2025-24042
- Published
- Feb 11, 2025
- Updated
- Feb 26, 2026
- Vendor
- Microsoft
- Product
- Visual Studio Code JavaScript Debugger
- Classifications
- CWE-284, T1574.008
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 11, 2025CVE publishedPublication date reported by the CVE source.
- Feb 26, 2026Record 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.97.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
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