Approved changes feed: RSS · Atom
cpe:2.3:a:google:bazel:*:*:*:*:*:visual_studio:*:*
part: a version: * update: *
| Vendor | Google (f181d1eb-7269-5bae-b76e-e66ceb214562) |
|---|---|
| Product | Bazel (7e116787-f446-5b27-9b07-e12aef3b0ba7) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | visual_studio |
| Target hardware | * |
| Other | * |
| Notes | Imported from purl2cpe mapping |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/bazelbuild/vscode-bazel |
purl2cpe | 2026-06-01 10:16:38.498220 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2022-3474 |
vulnerable | 2026-06-08 05:48:21.142812 |
Bazel leaks user credentials through the remote assets API
A bad credential handling in the remote assets API for Bazel versions prior to 5.3.2 and 4.2.3 sends all user-provided credentials instead of only the required ones for the requests. We recommend upgrading to versions later than or equal to 5.3.2 or 4.2.3.
Published: 2022-10-26T00:00:00.000Z
Updated: 2024-08-03T01:14:01.488Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2021-22539 |
vulnerable | 2026-06-08 05:30:00.824956 |
Code execution in VSCode-bazel via malicious Bazel config files
HIGH (8.2)
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.
Published: 2021-04-16T10:15:12.912Z
Updated: 2024-09-17T01:46:31.592Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.