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.
References
Link | Resource |
---|---|
https://github.com/bazelbuild/vscode-bazel-ghsa-2rcw-j8x4-hgcv/pull/1 | Broken Link |
https://github.com/bazelbuild/vscode-bazel/security/advisories/GHSA-2rcw-j8x4-hgcv | Third Party Advisory |
https://github.com/bazelbuild/vscode-bazel-ghsa-2rcw-j8x4-hgcv/pull/1 | Broken Link |
https://github.com/bazelbuild/vscode-bazel/security/advisories/GHSA-2rcw-j8x4-hgcv | Third Party Advisory |
Configurations
History
21 Nov 2024, 05:50
Type | Values Removed | Values Added |
---|---|---|
CVSS |
v2 : v3 : |
v2 : 6.8
v3 : 8.2 |
References | () https://github.com/bazelbuild/vscode-bazel-ghsa-2rcw-j8x4-hgcv/pull/1 - Broken Link | |
References | () https://github.com/bazelbuild/vscode-bazel/security/advisories/GHSA-2rcw-j8x4-hgcv - Third Party Advisory |
Information
Published : 2021-04-16 11:15
Updated : 2024-11-21 05:50
NVD link : CVE-2021-22539
Mitre link : CVE-2021-22539
CVE.ORG link : CVE-2021-22539
JSON object : View
Products Affected
- bazel