Code execution in VSCode-bazel via malicious Bazel config files
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Google LLC | VSCode-Bazel | affected |
|
No data.
No data available yet.
Vendor Solution
Upgrade vscode-bazel to version 0.4.1 or above
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2021-9680 | An attacker can place a crafted JSON config file into the project folder pointing to a custom executable. VScode-bazel allows the workspace path to lint *.bzl files to be set via this config file. As such the attacker is able to execute any executable on the system through vscode-bazel. We recommend upgrading to version 0.4.1 or above. |
No CVSS v4.0
No CVSS v3.0
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.310% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.