Hashicorp VaultWordPress extension · Jenkins
CVE-2023-33001
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 · uneditedJenkins 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.
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 confidenceJenkins HashiCorp Vault Plugin versions 360.v0a_1c04cf807d and earlier fails to mask credentials with asterisks in build logs when push mode for durable task logging is enabled, causing plaintext credential exposure.
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
Hashicorp VaultWordPress extension
<= 360.v0a_1c04cf807dCVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed HashiCorp Vault Plugin versionNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab, or check the plugin file in $JENKINS_HOME/plugins/hashicorp-vault directory for the .jpi or .hpi file's manifest versionAffected if Installed version is 360.v0a_1c04cf807d or earlier (note: 360.v0a_1c04cf807d itself is also affected)
-
Determine if durable task logging push mode is enabledCheck the Jenkins configuration for HashiCorp Vault Plugin settings. This is typically found in Manage Jenkins > Configure System > HashiCorp Vault Plugin configuration, or inspect the Jenkins configuration XML file (config.xml) for any 'vault-plugin' or ' durableTask' related settings with push mode enabledAffected if Push mode for durable task logging is enabled in the plugin configuration
-
Review recent build logs for exposed credentialsExamine recent build logs in Jenkins (build console output) where the HashiCorp Vault Plugin credentials were used, looking for plaintext values that should have been masked with asterisksAffected if Build logs contain plaintext credentials instead of masked asterisks when the plugin retrieves secrets during builds
User is affected if they have HashiCorp Vault Plugin version 360.v0a_1c04cf807d or earlier AND have push mode for durable task logging enabled, AND have build logs showing unmasked credentials
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate HashiCorp Vault Plugin to the patched version. Review existing build logs for exposed credentials and rotate any credentials that may have been logged.
Fix this in Hashicorp Vault
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-33001 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-33001 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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