CVE-2021-22539

Code execution via workspace-controlled Buildifier path

Published Apr 16, 2021 · Updated Sep 17, 2024

External path control in Google Bazel for Visual Studio Code 0.1.0 through 0.4.0 allows attackers to run a local executable. The extension accepts the workspace-scoped bazel.buildifierExecutable setting from .vscode/settings.json and invokes that path to lint .bzl files. A victim must open the malicious project and trigger linting; the chosen program then runs with the victim's VS Code privileges.

CVSS severity8.2
High
EPSS probability0.31%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

External path control in Google Bazel for Visual Studio Code 0.1.0 through 0.4.0 allows attackers to run a local executable. The extension accepts the workspace-scoped bazel.buildifierExecutable setting from .vscode/settings.json and invokes that path to lint .bzl files. A victim must open the malicious project and trigger linting; the chosen program then runs with the victim's VS Code privileges.

The record

CVE
CVE-2021-22539
Published
Apr 16, 2021
Updated
Sep 17, 2024
Vendor
Google
Product
Bazel for Visual Studio Code
Classifications
CWE-668, CWE-73, T1204.002
Attack vector
local
Privileges
Unavailable

Timeline

How it unfolded

  1. Apr 16, 2021CVE publishedPublication date reported by the CVE source.
  2. Sep 17, 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?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=unspecified <=0.4.0

What conditions does exploitation require?

Attack vectorlocal
Required privilegesUnavailable in this record.

What is affected?

Google · Bazel for Visual Studio Codeversion=unspecified <=0.4.0

Published CVSS scores

7.8NIST NVDCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
8.2GitHub AdvisoryCVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H

CVSS describes severity. EPSS estimates exploitation probability.

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.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
PrivilegesUnavailable
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-668Exposure of Resource to Wrong Sphere
CWE-73External Control of File Name or Path
T1204.002User Execution: Malicious File

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