GPU VulnDB

Database/Control plane, storage & DevOps

Jenkins Azure CLI Plugin: Item/Configure permission becomes arbitrary shell execution on the controller

CVSS 8.8CVE-2025-64140Control plane, storage & DevOpscurated

Impact

Azure CLI Plugin 0.9 and earlier does not restrict which commands it runs, so any user who can configure a job turns Item/Configure into arbitrary shell commands executing as the Jenkins service account on the controller itself - not on an agent. On a build controller that holds cloud credentials, registry push tokens, signing keys and kubeconfigs for the fleet, that is a credential-theft and supply-chain foothold: whoever gets it can poison the container images and model artifacts that later run on GPU nodes. The relevant question for an operator is who holds Item/Configure, which in most installations is a much wider group than administrators.

Who can reach it

Authenticated Jenkins user with Item/Configure permission, over the network to the Jenkins web interface. No controller shell access or administrator rights needed beforehand.

What to do

The Jenkins security advisory of 2025-10-29 (SECURITY-3538) lists no fixed version for this plugin, so treat it as mitigate-only until one ships: uninstall or disable the Azure CLI Plugin, or restrict Item/Configure to trusted administrators on any controller that keeps it. Removing a plugin requires a controller restart to take full effect - a short CI outage, no impact on GPU nodes. Rotate any Azure or cloud credentials the plugin had access to if untrusted users held Item/Configure.

References

Related entries

All Control plane, storage & DevOps entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.