Code execution via workspace-controlled linter path
Published Mar 24, 2021 · Updated Aug 3, 2024
Code injection in MATLAB for Visual Studio Code before 2.0.1 allows remote attackers to execute arbitrary code via a crafted workspace. The extension accepts workspace overrides for matlab.mlintpath and passes that value to its linter process, allowing a repository to select an attacker-controlled executable. Execution occurs when the workspace is opened with the extension and linting invokes the configured binary, granting code execution with the editor user's privileges.
Summary
What happened
Code injection in MATLAB for Visual Studio Code before 2.0.1 allows remote attackers to execute arbitrary code via a crafted workspace. The extension accepts workspace overrides for matlab.mlintpath and passes that value to its linter process, allowing a repository to select an attacker-controlled executable. Execution occurs when the workspace is opened with the extension and linting invokes the configured binary, granting code execution with the editor user's privileges.
The record
- CVE
- CVE-2021-28967
- Published
- Mar 24, 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 24, 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