dbcve.org
Hashicorp VaultApplication · Jenkins

CVE-2022-36888

MEDIUM · 6.5 CVSS v3.1 Published 2022-07-27
Fix available
A fix is available. Upgrade to after 354.vdb_858fd6b_f48 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
A missing permission check in Jenkins HashiCorp Vault Plugin 354.vdb_858fd6b_f48 and earlier allows attackers with Overall/Read permission to obtain credentials stored in Vault with attacker-specified path and keys.

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 confidence

The HashiCorp Vault Plugin for Jenkins versions 354.vdb_858fd6b_f48 and earlier lacks proper permission checks, allowing any user with Overall/Read permission to retrieve arbitrary credentials from Vault by specifying the path and keys. This is a classic broken access control vulnerability where the plugin assumes Overall/Read permission is sufficient for credential access, when in fact higher privileges should be required.

MitigationUpdate the HashiCorp Vault Plugin to version 354.vdb_858fd6b_f48 or later which includes the missing permission check. Until patched, limit Overall/Read permission to trusted users only and audit existing users.

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 VaultApplication
Affected:<= 354.vdb_858fd6b_f48

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Check installed HashiCorp Vault Plugin version
    Navigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'HashiCorp Vault' or access /pluginManager/pluginStatistics to view plugin versions. Alternatively, check the file $JENKINS_HOME/plugins/hashicorp-vault-plugin/META-INF/MANIFEST.MF for the Implementation-Version.
    Affected if The plugin version is 354.vdb_858fd6b_f48 or earlier.
  2. Verify Vault plugin configuration exists
    Check if the HashiCorp Vault Plugin is configured with Vault credentials. Navigate to Manage Jenkins > Configure System > HashiCorp Vault or check the configuration file $JENKINS_HOME/org.jenkinsci.plugins.hashicorpvaultplugin.HashicorpVaultPlugin.xml.
    Affected if The plugin is installed and has Vault credentials configured.
  3. Identify users with Overall/Read permission
    Navigate to Manage Jenkins > Manage Users or check $JENKINS_HOME/users/ directory. Review user permissions via Manage Jenkins > Manage and Assign Permissions > Matrix-based security or Project-based Matrix Authorization Strategy.
    Affected if Any user account has Overall/Read permission assigned.
  4. Check for Vault credential bindings in jobs
    Review Jenkins jobs that use the 'withVault' pipeline step or Vault Credential Binding build steps. Check job configurations in $JENKINS_HOME/jobs/*/config.xml for '<com.dabsquared.gitlabjenkins.connection.GitLabConnection>' or look for 'vault' related configuration elements.
    Affected if Jobs are configured to use Vault credentials, which could be retrieved by any user with Overall/Read permission.

You are affected if the HashiCorp Vault Plugin version is 354.vdb_858fd6b_f48 or earlier, the plugin has Vault credentials configured, and any user with basic Overall/Read permission exists in Jenkins.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 354.vdb_858fd6b_f48
Interim mitigation

Update the HashiCorp Vault Plugin to version 354.vdb_858fd6b_f48 or later which includes the missing permission check. Until patched, limit Overall/Read permission to trusted users only and audit existing users.

Recommended fix Moderate confidence

HashiCorp Vault Plugin version newer than 354.vdb_858fd6b_f48 (check Jenkins plugin repository or Jenkins security advisories for exact fixed version)

  1. Navigate to Jenkins Dashboard > Manage Jenkins > Manage Plugins
  2. Select the 'Installed' tab and locate the 'HashiCorp Vault Plugin'
  3. If an update is available, select the plugin and click 'Update'
  4. Restart Jenkins to apply the plugin update
  5. Verify the plugin version has been updated to a version newer than 354.vdb_858fd6b_f48

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Hashicorp Vault Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-36888 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-36888 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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