Consul Kv BuilderApplication · Jenkins
CVE-2023-30531
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 Consul KV Builder Plugin 2.0.13 and earlier does not mask the HashiCorp Consul ACL Token on the global configuration form, increasing the potential for attackers to observe and capture it.
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 confidenceThe Jenkins Consul KV Builder Plugin version 2.0.13 and earlier displays the HashiCorp Consul ACL Token in plain text on the global configuration form instead of masking it as a password field, allowing authenticated users to view the sensitive token.
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
Consul Kv BuilderApplication
<= 2.0.13CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Verify Consul KV Builder Plugin is installedNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed and search for 'Consul KV Builder' or 'consul' in the plugin list. Confirm the plugin appears in the installed plugins.Affected if The Consul KV Builder Plugin is present in the Jenkins instance.
-
Determine installed plugin versionIn the Manage Plugins > Installed section, locate the Consul KV Builder Plugin and record the version number displayed in the Version column.Affected if The installed version is 2.0.13 or earlier.
-
Access global configuration pageNavigate to Jenkins > Manage Jenkins > Configure System and locate the 'Consul KV Builder' or 'Consul' configuration section. This requires authentication and appropriate Jenkins permissions.Affected if You can access the global configuration page as an authenticated user.
-
Inspect ACL Token field maskingIn the Consul KV Builder configuration section, locate the 'ACL Token' or 'Token' field. Observe whether the input displays as masked/dots (password field) or as plain readable text.Affected if The ACL Token field displays in plain text rather than being masked as a password field.
A user is affected if the Consul KV Builder Plugin version is 2.0.13 or earlier AND the ACL Token field on the global configuration form shows plain text instead of masked characters.
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 to a patched version of the plugin that masks the ACL token field. If no patch is available, restrict access to the global configuration page to only trusted administrators.
Fix this in Consul Kv Builder
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-30531 — 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-30531 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