CVE-2022-36883: High severity jenkins Git Jenkins vulnerability
A missing permission check in Jenkins Git Plugin 4.11.3 and earlier allows unauthenticated attackers to trigger builds of jobs configured to use an attacker-specified Git repository and to cause them to check out an attacker-specified commit.
Other sources
Git Plugin provides a webhook endpoint at /git/notifyCommit that can be used to notify Jenkins of changes to an SCM repository. For its most basic functionality, this endpoint receives a repository URL, and Jenkins will schedule polling for all jobs configured with the specified repository. In Git Plugin 4.11.3 and earlier, this endpoint can be accessed with GET requests and without authentication. In addition to this basic functionality, the endpoint also accept a sha1 parameter specifying a commit ID. If this parameter is specified, jobs configured with the specified repo will be triggered immediately, and the build will check out the specified commit. Additionally, the output of the webhook endpoint will provide information about which jobs were triggered or scheduled for polling, including jobs the user has no permission to access. This allows attackers with knowledge of Git repository URLs to trigger builds of jobs using a specified Git repository and to cause them to check out an attacker-specified commit, and to obtain information about the existence of jobs configured with this Git repository. Git Plugin 4.11.4 requires a token parameter which will act as an authentication for the webhook endpoint. While GET requests remain allowed, attackers would need to be able to provide a webhook token. For more information see the plugin documentation.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
redhat/jenkinsto a version that resolves this vulnerability.Fixed in 2-plugins-0:4.10.1675144701-1.el8 - Upgrade
Upgrade
redhat/jenkinsto a version that resolves this vulnerability.Fixed in 2-plugins-0:4.8.1672842762-1.el8 - Upgrade
Upgrade
redhat/jenkinsto a version that resolves this vulnerability.Fixed in 2-plugins-0:4.9.1675668922-1.el8 - Upgrade
Upgrade
maven/org.jenkins-ci.plugins:gitto a version that resolves this vulnerability.Fixed in 4.11.4 - Upgrade
Upgrade
redhat/gitto a version that resolves this vulnerability.Fixed in 4.11.4 - Upgrade
Upgrade
Jenkins Git Pluginto a version that resolves this vulnerability.Fixed in 4.11.4
Event History
Parent advisories
This vulnerability appears in the following advisories.
Frequently Asked Questions
What is the severity of CVE-2022-36883?
CVE-2022-36883 is classified as a high severity vulnerability due to its potential for unauthenticated remote code execution.
Who is affected by CVE-2022-36883?
CVE-2022-36883 affects Jenkins Git Plugin versions 4.11.3 and earlier.
How do I fix CVE-2022-36883?
To fix CVE-2022-36883, update the Jenkins Git Plugin to version 4.11.4 or later.
What type of attack can be executed through CVE-2022-36883?
An attacker can trigger unauthorized builds using a specified Git repository and commit due to the missing permission check in CVE-2022-36883.
What systems are vulnerable to CVE-2022-36883?
Systems running Jenkins with the affected versions of the Git Plugin are vulnerable to CVE-2022-36883.