Hashicorp VaultApplication · Jenkins
CVE-2022-25186
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 3.8.0 and earlier implements functionality that allows agent processes to retrieve any Vault secrets for use on the agent, allowing attackers able to control agent processes to obtain Vault secrets for an attacker-specified path and key.
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 · moderate confidenceThe HashiCorp Vault Plugin for Jenkins versions 3.8.0 and earlier allows agent processes to retrieve any Vault secrets without proper access restrictions. Attackers who can control Jenkins agent processes can request secrets from arbitrary Vault paths and keys, bypassing intended secret access controls.
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
<= 3.8.0CVSS 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.
-
Identify the HashiCorp Vault Plugin versionIn the Jenkins web UI, navigate to Manage Jenkins > Manage Plugins > Installed tab, then search for 'HashiCorp Vault' or 'Vault Plugin' in the filter. The version number is displayed in the 'Version' column.Affected if The displayed version is 3.8.0 or earlier.
-
Verify Jenkins agents are configuredIn the Jenkins web UI, navigate to Manage Jenkins > Manage Nodes and Clouds. Review whether any permanent agents or cloud-based agents are defined and active.Affected if Any Jenkins agents (permanent nodes or cloud agents) are configured and connected to the controller.
-
Confirm Vault secret retrieval is used in agent buildsInspect existing Jenkins jobs that run on agents and check whether they use the 'vault' step or related Vault Plugin functionality to fetch secrets during build or pipeline execution.Affected if Agent-based jobs or pipelines use Vault plugin steps to retrieve secrets.
-
Review Vault access policies for agent principalsIf using the Jenkins Kubernetes authentication or other agent-based Vault auth methods, examine the associated Vault policies to determine what secret paths the agent service account is authorized to access.Affected if The Vault policy grants broad or unrestricted access to secret paths beyond what is strictly required for the agent builds.
If the HashiCorp Vault Plugin version is 3.8.0 or earlier AND Jenkins agents are configured and used to retrieve secrets, the environment is vulnerable to unauthorized secret access via agent process compromise.
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 dataUpgrade the HashiCorp Vault Plugin to a version beyond 3.8.0 that includes the access control fix, and review Vault secret access policies to ensure agent processes can only retrieve authorized secrets.
Fix this in Hashicorp Vault
Scoped from the published advisory
- Consultation3.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-25186 — 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-2022-25186 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