dbcve.org
Azure Key VaultApplication · Jenkins

CVE-2023-30514

HIGH · 7.5 CVSS v3.1 Published 2023-04-12
Fix available
A fix is available. Upgrade to after 187.va_cd5fecd198a or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Jenkins Azure Key Vault Plugin 187.va_cd5fecd198a_ and earlier does not properly mask (i.e., replace with asterisks) credentials in the build log when push mode for durable task logging is enabled.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Jenkins Azure Key Vault Plugin versions 187.va_cd5fecd198a_ and earlier fails to properly mask (replace with asterisks) credentials in build logs when push mode for durable task logging is enabled, resulting in plaintext credential exposure.

MitigationUpgrade the Azure Key Vault Plugin to the latest version. Alternatively, if immediate upgrade is not feasible, disable push mode for durable task logging until the patch can be applied.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Azure Key VaultApplication
Affected:<= 187.va_cd5fecd198a

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Azure Key Vault Plugin version
    Navigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab and search for 'Azure Key Vault', or use the Jenkins CLI: java -jar jenkins-cli.jar list-plugins | grep -i 'azure key vault'
    Affected if The installed version is 187.va_cd5fecd198a or earlier (any version <= 187.va_cd5fecd198a)
  2. Verify push mode for durable task logging is enabled
    Check the Jenkins configuration file (jenkins.model.JenkinsLocationConfiguration.xml) for the property 'org.jenkinsci.plugins.workflow.durable_task.DurableTaskStep$DescriptorImpl.pushMode=true', or navigate to: Manage Jenkins > System Configuration > System > scroll to 'Durable Task' settings and check if push mode is enabled
    Affected if Push mode for durable task logging is enabled in the Jenkins configuration

A user is affected if they have Azure Key Vault Plugin version 187.va_cd5fecd198a or earlier AND have push mode for durable task logging enabled, as both conditions must be true for the credential masking failure to occur.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 187.va_cd5fecd198a
Interim mitigation

Upgrade the Azure Key Vault Plugin to the latest version. Alternatively, if immediate upgrade is not feasible, disable push mode for durable task logging until the patch can be applied.

Fix this in Azure Key Vault Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-30514 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-30514 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data