Code execution via workspace-scoped executable path
Published Mar 31, 2021 · Updated Aug 3, 2024
Code execution in the unofficial vscode-rufo extension before 0.0.4 allows attackers to run arbitrary binaries through a crafted workspace. The rufo.exe configuration accepted a workspace-scoped path, so opening attacker-controlled workspace settings caused the extension to invoke the selected executable. Exploitation requires a user to open the crafted folder, after which the binary runs with the user's Visual Studio Code privileges.
Summary
What happened
Code execution in the unofficial vscode-rufo extension before 0.0.4 allows attackers to run arbitrary binaries through a crafted workspace. The rufo.exe configuration accepted a workspace-scoped path, so opening attacker-controlled workspace settings caused the extension to invoke the selected executable. Exploitation requires a user to open the crafted folder, after which the binary runs with the user's Visual Studio Code privileges.
The record
- CVE
- CVE-2021-29658
- Published
- Mar 31, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 31, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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