# CVE-2023-33001: Jenkins HashiCorp Vault Plugin has improper masking of credentials

> Attackers can read exposed credentials in build logs when push mode for durable task logging is enabled in the Jenkins HashiCorp Vault Plugin.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 May 2023
- **Updated:** 23 Jan 2025
- **Also known as:** GHSA-v3fv-v9m6-26g3

## What is CVE-2023-33001?

CVE-2023-33001 is a high-severity vulnerability in Jenkins HashiCorp Vault Plugin, published on 16 May 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Jenkins HashiCorp Vault Plugin 360.v0a_1c04cf807d 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.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

## Which versions are affected by CVE-2023-33001?

2 open source packages ship an affected version, including com.datapipe.jenkins.plugins:hashicorp-vault-plugin. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `com.datapipe.jenkins.plugins:hashicorp-vault-plugin` | Maven | All versions to 360.v0a | None |
| `com.datapipe.jenkins.plugins:hashicorp-vault-plugin` | Maven | All versions to 360.v0a | None |

Products: Jenkins Hashicorp Vault.

## How do I fix CVE-2023-33001?

No fix has been published for CVE-2023-33001 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-33001 being exploited?

There is no known exploitation of CVE-2023-33001 in the wild and no public exploit code.

## Other vulnerabilities in Jenkins HashiCorp Vault Plugin

- [CVE-2022-36888](https://insights.sbomify.com/CVE-2022-36888/): Jenkins HashiCorp Vault Plugin does not perform permission checks in several HTTP endpoints that perform Vault connection tests (medium 6.5)
- [CVE-2022-25186](https://insights.sbomify.com/CVE-2022-25186/): Agent-to-controller security bypass in Jenkins HashiCorp Vault Plugin (medium 6.5)
- [CVE-2022-25197](https://insights.sbomify.com/CVE-2022-25197/): Agent-to-controller security bypass in Jenkins HashiCorp Vault Plugin allows reading arbitrary files (medium 6.5)
- [CVE-2022-23109](https://insights.sbomify.com/CVE-2022-23109/): Improper credentials masking in Jenkins HashiCorp Vault Plugin (medium 6.5)
- [CVE-2025-67642](https://insights.sbomify.com/CVE-2025-67642/): Jenkins HashiCorp Vault Plugin exposes system-scoped Vault credentials (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-33001 and fix it if it is affected.

What it is: CVE-2023-33001 is a high-severity vulnerability in Jenkins HashiCorp Vault Plugin, published on 16 May 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-33001 in the wild and no public exploit code.

Affected packages and fixed versions:
- com.datapipe.jenkins.plugins:hashicorp-vault-plugin (Maven): affected all versions up to 360.v0a; no fix listed
- com.datapipe.jenkins.plugins:hashicorp-vault-plugin (Maven): affected all versions up to 360.v0a; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-33001/ (Markdown: https://insights.sbomify.com/CVE-2023-33001/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-33001
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-33001
- OSV: https://osv.dev/vulnerability/CVE-2023-33001

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-33001/
Summaries are generated and may contain mistakes; the official description above is the record.