Code execution via workspace-controlled executable path
Published Mar 18, 2021 · Updated Aug 3, 2024
Code execution in ShellCheck for Visual Studio Code before 0.13.4 allows context-dependent attackers to run binaries via a crafted workspace. The extension accepts shellcheck.executablePath from workspace configuration and launches the referenced binary instead of restricting that setting to machine scope. A user must open an attacker-controlled workspace; the binary then runs with that user's Visual Studio Code privileges.
Summary
What happened
Code execution in ShellCheck for Visual Studio Code before 0.13.4 allows context-dependent attackers to run binaries via a crafted workspace. The extension accepts shellcheck.executablePath from workspace configuration and launches the referenced binary instead of restricting that setting to machine scope. A user must open an attacker-controlled workspace; the binary then runs with that user's Visual Studio Code privileges.
The record
- CVE
- CVE-2021-28794
- Published
- Mar 18, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-284, T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 18, 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.
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