Jenkins Kubernetes Plugin does not properly mask credentials

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

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

EPSS

• CVE-2023-30513: 0.50% estimated exploitation activity in the next 30 days; percentile 42.51 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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…

Published by the source

12 Apr 2023, 18:30 UTC

Last modified by the source

21 Apr 2023, 18:49 UTC

Source last checked

26 Oct 2026, 16:11 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-v5hq-cqqr-6w4g

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2023-30513

Advisory: Jenkins Kubernetes Plugin does not properly mask credentials
IDs: CVE-2023-30513, GHSA-v5hq-cqqr-6w4g
Record: https://patchnext.com/advisories/cve-2023-30513 (revision 1, source checked 26 Oct 2026, 16:11 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.csanchez.jenkins.plugins:kubernetes 3910.ve59cec5e33ea. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.csanchez.jenkins.plugins:kubernetes: affected < 3910.ve59cec5e33ea; fixed in 3910.ve59cec5e33ea

## Suggested inspection (read-only)
- Maven org.csanchez.jenkins.plugins:kubernetes: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.csanchez.jenkins.plugins:kubernetes.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-v5hq-cqqr-6w4g (GitHub-reviewed advisory GHSA-v5hq-cqqr-6w4g lists affected ranges: Maven org.csanchez.jenkins.plugins:kubernetes >=0 <3910.ve59cec5e33ea)

Commands are suggestions: review each one before running it.