CVE-2022-41238
First published: Wed Sep 21 2022(Updated: )
A missing permission check in Jenkins DotCi Plugin 2.40.00 and earlier allows unauthenticated attackers to trigger builds of jobs corresponding to the attacker-specified repository for attacker-specified commits.
Credit: jenkinsci-cert@googlegroups.com jenkinsci-cert@googlegroups.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Jenkins Dotci | <=2.40.00 |
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.
Frequently Asked Questions
What is the severity of CVE-2022-41238?
CVE-2022-41238 is classified as a high severity vulnerability due to its potential for unauthenticated remote code execution.
How do I fix CVE-2022-41238?
To mitigate CVE-2022-41238, upgrade the Jenkins DotCi Plugin to version 2.40.01 or later, which includes the necessary permission checks.
What does CVE-2022-41238 allow attackers to do?
CVE-2022-41238 allows unauthenticated attackers to trigger builds of jobs in Jenkins using attacker-specified repositories and commits.
Which versions of Jenkins DotCi Plugin are affected by CVE-2022-41238?
CVE-2022-41238 affects Jenkins DotCi Plugin versions 2.40.00 and earlier.
Is there a workaround for CVE-2022-41238 if I cannot upgrade?
There is no known workaround for CVE-2022-41238, so upgrading is the recommended action to secure the Jenkins instance.
- collector/nvd-index
- collector/nvd-api
- agent/author
- agent/type
- collector/mitre-cve
- source/MITRE
- agent/weakness
- agent/references
- agent/severity
- agent/last-modified-date
- agent/softwarecombine
- agent/event
- agent/description
- agent/first-publish-date
- agent/tags
- agent/source
- vendor/jenkins
- canonical/jenkins dotci
- version/jenkins dotci/2.40.00