HashiCorp Vault Plugin 360.v0a_1c04cf807d and earlier does not properly mask (i.e., replace with asterisks) credentials printed in the build log from Pipeline steps likeshandbat, when both of the following conditions are met:
The credentials are printed in build steps executing on an agent (typically inside anodeblock).
| An improvement in Credentials Binding 523.525.vb_72269281873 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.
-- | --
Improper masking of credentials in HashiCorp Vault Plugin
SECURITY-3077 / CVE-2023-33001
Severity (CVSS): [Medium](https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N)
Affected plugin: [hashicorp-vault-plugin](https://plugins.jenkins.io/hashicorp-vault-plugin)
Description:
HashiCorp Vault Plugin 360.v0a_1c04cf807d 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](https://plugins.jenkins.io/workflow-durable-task-step/) that can be enabled through the [Java system property](https://www.jenkins.io/doc/book/managing/system-properties/) org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep.USE_WATCHING. It is also automatically enabled by some plugins, e.g., [OpenTelemetry](https://plugins.jenkins.io/opentelemetry/) and [Pipeline Logging over CloudWatch](https://plugins.jenkins.io/pipeline-cloudwatch-logs/).
An improvement in [Credentials Binding](https://plugins.jenkins.io/credentials-binding/) 523.525.vb_72269281873 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.
### What Operating System are you using (both controller, and any agents involved in the problem)?
N/A
### Reproduction steps
this is specific the Jenkins plug-in HashiCorp Vault Plugin vulnerability, which is already published by Jenkins CNA. requesting to update, when can we have a new version of Hashicorp Vault plugin fixing this vuln.
### Expected Results
This is specific the Jenkins plug-in HashiCorp Vault Plugin vulnerability, which is already published by Jenkins CNA. Requesting to update, when can we have a new version of Hashicorp Vault plugin fixing this vulnerability.
### Actual Results
Explained in the description
### Anything else?
_No response_
icep87
commented
1 year ago
Jenkins and plugins versions report
Improper masking of credentials in HashiCorp Vault Plugin
SECURITY-3077 / CVE-2023-33001Severity (CVSS): Medium
Affected plugin:
hashicorp-vault-pluginDescription:
HashiCorp Vault Plugin 360.v0a_1c04cf807d and earlier does not properly mask (i.e., replace with asterisks) credentials printed in the build log from Pipeline steps like
shandbat, when both of the following conditions are met:The credentials are printed in build steps executing on an agent (typically inside a
nodeblock).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.durable_task.DurableTaskStep.USE_WATCHING. It is also automatically enabled by some plugins, e.g., OpenTelemetry and Pipeline Logging over CloudWatch.