Jenkins Gitlab vulnerabilities

6 vulnerabilities

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

4.3CVE-2025-24397jenkins projectjenkins gitlab plugin+2
EPSS score
0.30%
An incorrect permission check in Jenkins GitLab Plugin 1.9.6 and earlier allows attackers with global Item/Configure permission (while lacking Item/Configure permission on any particular job) to enumerate credential IDs of GitLab API token and Secret text credentials stored in Jenkins.5.3CVE-2022-43411jenkins projectjenkins gitlab plugin+2
EPSS score
0.80%
Jenkins GitLab Plugin 1.5.35 and earlier uses a non-constant time comparison function when checking whether the provided and expected webhook token are equal, potentially allowing attackers to use statistical methods to obtain a valid webhook token.6.5CVE-2022-30955jenkins projectjenkins gitlab plugin+2
EPSS score
0.90%
Jenkins GitLab Plugin 1.5.31 and earlier does not perform a permission check in an HTTP endpoint, allowing attackers with Overall/Read permission to enumerate credentials IDs of credentials stored in Jenkins.5.4CVE-2022-34777jenkins projectjenkins gitlab plugin+2
EPSS score
73.06%
Jenkins GitLab Plugin 1.5.34 and earlier does not escape multiple fields inserted into the description of webhook-triggered builds, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers with Item/Configure permission.8CVE-2019-10300jenkins projectjenkins gitlab plugin+2
EPSS score
1.33%
A cross-site request forgery vulnerability in Jenkins GitLab Plugin 1.5.11 and earlier in the GitLabConnectionConfig#doTestConnection form validation method allowed attackers to connect to an attacker-specified URL using attacker-specified credentials IDs obtained through another method, capturing credentials stored in Jenkins.8.8CVE-2019-10301jenkins projectjenkins gitlab plugin+2
EPSS score
1.35%
A missing permission check in Jenkins GitLab Plugin 1.5.11 and earlier in the GitLabConnectionConfig#doTestConnection form validation method allowed 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.