First published: Wed Jul 27 2022(Updated: )
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.
Credit: jenkinsci-cert@googlegroups.com jenkinsci-cert@googlegroups.com jenkinsci-cert@googlegroups.com
Affected Software | Affected Version | How to fix |
---|---|---|
maven/com.datapipe.jenkins.plugins:hashicorp-vault-plugin | <=354.vdb | 355.v3b_38d767a_b_a_8 |
HashiCorp Vault | <=354.vdb_858fd6b_f48 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2022-36888 boasts a high severity rating due to the potential for unauthorized access to sensitive credentials.
The fix for CVE-2022-36888 is to update the Jenkins HashiCorp Vault Plugin to version 355.v3b_38d767a_b_a_8 or later.
CVE-2022-36888 allows attackers with Overall/Read permission to exploit the vulnerability.
Versions up to and including 354.vdb_858fd6b_f48 of the Jenkins HashiCorp Vault Plugin are vulnerable to CVE-2022-36888.
Yes, CVE-2022-36888 can lead to the exposure of credentials stored in Vault through attacker-specified paths and keys.