Code execution during untrusted repository cloning
Published May 11, 2021 · Updated Aug 3, 2024
Remote code execution in Microsoft Visual Studio Code Dev Containers before 1.56 allows attackers to run code through repository cloning. Microsoft states that the Clone Repository in Container Volume flow executes code from a cloned repository without adequate user awareness, but no code-level cause is public. The victim must invoke the clone-into-volume workflow on an attacker-controlled repository, after which code runs with the extension host privileges.
Summary
What happened
Remote code execution in Microsoft Visual Studio Code Dev Containers before 1.56 allows attackers to run code through repository cloning. Microsoft states that the Clone Repository in Container Volume flow executes code from a cloned repository without adequate user awareness, but no code-level cause is public. The victim must invoke the clone-into-volume workflow on an attacker-controlled repository, after which code runs with the extension host privileges.
The record
- CVE
- CVE-2021-31213
- Published
- May 11, 2021
- Updated
- Aug 3, 2024
- Vendor
- Microsoft
- Product
- Visual Studio Code Dev Containers
- Classifications
- T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 11, 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.56
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