Jenkins Project Jenkins Git Plugin vulnerabilities

7 vulnerabilities

Known vulnerabilities in Jenkins Project Jenkins Git Plugin, newest first, with CVSS severity, EPSS, KEV listings, ransomware use and the affected versions.

6.1CVE-2021-21684jenkins projectjenkins git plugin+2
EPSS score
1.24%
Jenkins Git Plugin 4.8.2 and earlier does not escape the Git SHA-1 checksum parameters provided to commit notifications when displaying them in a build cause, resulting in a stored cross-site scripting (XSS) vulnerability.5.4CVE-2020-2136jenkins projectjenkins git plugin+2
EPSS score
0.85%
Jenkins Git Plugin 4.2.0 and earlier does not escape the error message for the repository URL for Microsoft TFS field form validation, resulting in a stored cross-site scripting vulnerability.5.3CVE-2022-36884jenkins projectjenkins git plugin+2
EPSS score
1.09%
The webhook endpoint in Jenkins Git Plugin 4.11.3 and earlier provide unauthenticated attackers information about the existence of jobs configured to use an attacker-specified Git repository.7.5CVE-2022-36883jenkins projectjenkins git plugin+2
EPSS score
7.00%
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.8.8CVE-2022-36882jenkins projectjenkins git plugin+2
EPSS score
0.74%
A cross-site request forgery (CSRF) vulnerability in Jenkins Git Plugin 4.11.3 and earlier allows 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.6.5CVE-2022-38663jenkins projectjenkins git plugin+2
EPSS score
0.94%
Jenkins Git Plugin 4.11.4 and earlier does not properly mask (i.e., replace with asterisks) credentials in the build log provided by the Git Username and Password (`gitUsernamePassword`) credentials binding.7.5CVE-2022-30947jenkins projectjenkins git plugin+4
EPSS score
1.30%
Jenkins Git Plugin 4.11.1 and earlier allows attackers able to configure pipelines to check out some SCM repositories stored on the Jenkins controller's file system using local paths as SCM URLs, obtaining limited information about other projects' SCM contents.