org.jenkins-ci.plugins:azure-keyvault

Open advisories

2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

1. Medium, CVSS 4.3MavenPublished 12 Apr 2023

   Jenkins Azure Key Vault Plugin does not properly mask credentials

   CVE-2023-30514 · GHSA-gmxm-pr58-v5jc

   Affected

   • Maven org.jenkins-ci.plugins:azure-keyvault < 188.vf46b

   Fixed in

   188.vf46b· Vendor fix available

   Issue

   Multiple Jenkins plugins do not properly mask (i.e., replace with asterisks) credentials printed in the build log from Pipeline steps like sh and bat, when both of the following conditions are met: - The credentials are printed in build steps executing on an agent (typically inside a node block). - Push mode for durable task logging is enabled. This is a hidden option in Pipeline: Nodes and Processes that can be enabled through the Java system property org.jenkinsci.plugins.workflow.steps.durabletask.DurableTaskStep.USEWATCHING. It is also automatically enabled by some plugins, e.g., OpenTelemetry and Pipeline Logging over CloudWatch. The following plugins are affected by this vulnerability: - Kubernetes 3909.v1f2c633e8590 and earlier (SECURITY-3079 / CVE-2023-30513) - Azure Key Vault 187.vacd5fecd198a and earlier (SECURITY-3051 / CVE-2023-30514) - Thycotic DevOps Secrets Vault 1.0.0 (SECURITY-3078 / CVE-2023-30515) The following plugins have been updated to properly mask credentials…

   Recommended action: Upgrade to 188.vf46b (pre-release) or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

   Sources:github.comSource checked 26 Oct 2026, 16:11 UTCEvidence →
2. Medium, CVSS 4.3MavenPublished 24 May 2022

   Missing permission checks in Jenkins Azure Key Vault Plugin allow enumerating credentials IDs

   CVE-2020-2313 · GHSA-gf8w-6hcm-rh3j

   Affected

   • Maven org.jenkins-ci.plugins:azure-keyvault < 2.1

   Fixed in

   2.1· Vendor fix available

   Issue

   Jenkins Azure Key Vault Plugin 2.0 and earlier does not perform permission checks in several HTTP endpoints. This allows attackers with Overall/Read permission to enumerate credentials IDs of credentials stored in Jenkins. Those can be used as part of an attack to capture the credentials using another vulnerability. An enumeration of credentials IDs in Jenkins Azure Key Vault Plugin 2.1 requires the appropriate permissions.

   Recommended action: Upgrade to 2.1 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

   Sources:github.comSource checked 26 Oct 2026, 16:21 UTCEvidence →