CVE-2022-36921
First published: Wed Jul 27 2022(Updated: )
A missing permission check in Jenkins Coverity Plugin 1.11.4 and earlier allows attackers with Overall/Read permission to connect to an attacker-specified URL using attacker-specified credentials IDs obtained through another method, capturing credentials stored in Jenkins.
Credit: jenkinsci-cert@googlegroups.com jenkinsci-cert@googlegroups.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Jenkins Coverity | <=1.11.4 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2022-36921?
CVE-2022-36921 has a high severity rating due to the potential for unauthorized access and credential theft.
How do I fix CVE-2022-36921?
To fix CVE-2022-36921, update the Jenkins Coverity Plugin to version 1.11.5 or later.
What are the affected versions for CVE-2022-36921?
CVE-2022-36921 affects Jenkins Coverity Plugin versions up to and including 1.11.4.
What is the impact of CVE-2022-36921?
The impact of CVE-2022-36921 includes the possibility of credential leakage and unauthorized access to external systems.
Who is vulnerable to CVE-2022-36921?
Users of Jenkins with the Coverity Plugin installed prior to version 1.11.5 are vulnerable to CVE-2022-36921.
- collector/nvd-index
- collector/nvd-api
- agent/author
- agent/type
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/references
- agent/weakness
- agent/severity
- agent/last-modified-date
- agent/description
- agent/tags
- agent/event
- agent/first-publish-date
- agent/source
- vendor/jenkins
- canonical/jenkins coverity
- version/jenkins coverity/1.11.4