Remote code execution via workspace tool-path settings
Published Apr 13, 2021 · Updated Aug 3, 2024
Remote code execution in Microsoft Kubernetes Tools before 1.3.0 allows local users to execute code by opening a crafted workspace. The extension accepts workspace-scoped kubectl, Helm, and Minikube path settings and launches the referenced executable without excluding untrusted workspace configuration. Exploitation requires a user to open an attacker-controlled workspace and invoke a feature that runs a configured tool, granting code execution with the user's privileges.
Summary
What happened
Remote code execution in Microsoft Kubernetes Tools before 1.3.0 allows local users to execute code by opening a crafted workspace. The extension accepts workspace-scoped kubectl, Helm, and Minikube path settings and launches the referenced executable without excluding untrusted workspace configuration. Exploitation requires a user to open an attacker-controlled workspace and invoke a feature that runs a configured tool, granting code execution with the user's privileges.
The record
- CVE
- CVE-2021-28448
- Published
- Apr 13, 2021
- Updated
- Aug 3, 2024
- Vendor
- Microsoft
- Product
- Kubernetes Tools
- Classifications
- T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 13, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.0.0 <1.3.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