Code execution via workspace-controlled linter path
Published Apr 16, 2021 · Updated Aug 3, 2024
Remote code execution in Laurent Tréguier RPM Specfile support in VSCode before 0.3.2 allows remote attackers to run arbitrary binaries. The extension reads rpmspec.rpmlintPath from workspace settings and launches that configured path when linting RPM spec files, so a repository can select an attacker-controlled executable. The crafted workspace must be loaded with the extension enabled and linting active; resulting code runs with the VS Code user's privileges.
Summary
What happened
Remote code execution in Laurent Tréguier RPM Specfile support in VSCode before 0.3.2 allows remote attackers to run arbitrary binaries. The extension reads rpmspec.rpmlintPath from workspace settings and launches that configured path when linting RPM spec files, so a repository can select an attacker-controlled executable. The crafted workspace must be loaded with the extension enabled and linting active; resulting code runs with the VS Code user's privileges.
The record
- CVE
- CVE-2021-31414
- Published
- Apr 16, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-284, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 16, 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