Jenkins HashiCorp Vault Plugin has improper masking of 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-33001: 0.61% estimated exploitation activity in the next 30 days; percentile 49.04 (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.

Jenkins HashiCorp Vault Plugin 360.v0a1c04cf807d and earlier does 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. An improvement in Credentials Binding 523.525.vb72269281873 implements a workaround that applies build log masking even in affected plugins. This workaround is temporary and potentially incomplete, so it is still recommended that affected plugins be updated to resolve this issue. As of publication of this advisory,…

Published by the source

16 May 2023, 18:30 UTC

Last modified by the source

7 Nov 2023, 05:05 UTC

Source last checked

26 Oct 2026, 16:16 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-v3fv-v9m6-26g3

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

# Patch Next advisory brief: CVE-2023-33001

Advisory: Jenkins HashiCorp Vault Plugin has improper masking of credentials
IDs: CVE-2023-33001, GHSA-v3fv-v9m6-26g3
Record: https://patchnext.com/advisories/cve-2023-33001 (revision 1, source checked 26 Oct 2026, 16:16 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 response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven com.datapipe.jenkins.plugins:hashicorp-vault-plugin: affected <= 360.v0a

## Suggested inspection (read-only)
- Maven com.datapipe.jenkins.plugins:hashicorp-vault-plugin: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on com.datapipe.jenkins.plugins:hashicorp-vault-plugin.
- 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-v3fv-v9m6-26g3 (GitHub-reviewed advisory GHSA-v3fv-v9m6-26g3 lists affected ranges: Maven com.datapipe.jenkins.plugins:hashicorp-vault-plugin >=0 <=360.v0a)

Commands are suggestions: review each one before running it.