First published: Fri Apr 16 2021(Updated: )
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.
Credit: cve-coordination@google.com
Affected Software | Affected Version | How to fix |
---|---|---|
Google Bazel | >=0.1.0<0.4.1 |
Upgrade vscode-bazel to version 0.4.1 or above
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2021-22539 has a medium severity, as it allows for arbitrary code execution through a crafted JSON config file.
To fix CVE-2021-22539, update to Bazel version 0.4.2 or later, which addresses this vulnerability.
The impact of CVE-2021-22539 is that an attacker can execute any arbitrary executable on the system via a malicious config file.
CVE-2021-22539 affects Bazel versions from 0.1.0 to 0.4.1.
An attacker can exploit CVE-2021-22539 by placing a malicious JSON config file in the project folder that points to a custom executable.