Azure Setup Kubectl
Approved changes feed: RSS · Atom
cpe:2.3:a:microsoft:azure_setup_kubectl:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Microsoft (67206627-3ef6-5870-9d98-26a9f2e7065c) |
|---|---|
| Product | Azure Setup Kubectl (cc17fae4-7f18-5223-8c6b-8a6f5e62dd36) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from purl2cpe mapping |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/azure/setup-kubectl |
purl2cpe | 2026-06-01 10:17:05.904447 |
pkg:npm/azure-pipelines-tasks-kubernetes-common-v2 |
purl2cpe | 2026-06-01 10:17:05.904449 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2023-23939 |
vulnerable | 2026-06-03 14:49:29.111109 |
Azure/setup-kubectl: Escalation of privilege vulnerability for v3 and lower
LOW (3.9)
Azure/setup-kubectl is a GitHub Action for installing Kubectl. This vulnerability only impacts versions before version 3. An insecure temporary creation of a file allows other actors on the Actions runner to replace the Kubectl binary created by this action because it is world writable. This Kubectl tool installer runs `fs.chmodSync(kubectlPath, 777)` to set permissions on the Kubectl binary, however, this allows any local user to replace the Kubectl binary. This allows privilege escalation to the user that can also run kubectl, most likely root. This attack is only possible if an attacker somehow breached the GitHub actions runner or if a user is utilizing an Action that maliciously executes this attack. This has been fixed and released in all versions `v3` and later. 775 permissions are used instead. Users are advised to upgrade. There are no known workarounds for this issue.
Published: 2023-03-06T18:19:05.155Z
Updated: 2025-02-25T15:00:56.243Z |
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.