Vulnerabilities (CVE)

Filtered by vendor Jenkins Subscribe
Filtered by product Github Branch Source
Total 6 CVE
CVE Vendors Products Updated CVSS v2 CVSS v3
CVE-2024-23902 1 Jenkins 1 Github Branch Source 2024-01-31 N/A 4.3 MEDIUM
A cross-site request forgery (CSRF) vulnerability in Jenkins GitLab Branch Source Plugin 684.vea_fa_7c1e2fe3 and earlier allows attackers to connect to an attacker-specified URL.
CVE-2024-23903 1 Jenkins 1 Github Branch Source 2024-01-31 N/A 5.3 MEDIUM
Jenkins GitLab Branch Source Plugin 684.vea_fa_7c1e2fe3 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.
CVE-2024-23901 1 Jenkins 1 Github Branch Source 2024-01-31 N/A 6.5 MEDIUM
Jenkins GitLab Branch Source Plugin 684.vea_fa_7c1e2fe3 and earlier unconditionally discovers projects that are shared with the configured owner group, allowing attackers to configure and share a project, resulting in a crafted Pipeline being built by Jenkins during the next scan of the group.
CVE-2018-1000185 1 Jenkins 1 Github Branch Source 2023-12-10 4.0 MEDIUM 4.3 MEDIUM
A server-side request forgery vulnerability exists in Jenkins GitHub Branch Source Plugin 2.3.4 and older in Endpoint.java that allows attackers with Overall/Read access to cause Jenkins to send a GET request to a specified URL.
CVE-2017-1000087 1 Jenkins 1 Github Branch Source 2023-12-10 4.0 MEDIUM 4.3 MEDIUM
GitHub Branch Source provides a list of applicable credential IDs to allow users configuring a job to select the one they'd like to use. This functionality did not check permissions, allowing any user with Overall/Read permission to get a list of valid credentials IDs. Those could be used as part of an attack to capture the credentials using another vulnerability.
CVE-2017-1000091 1 Jenkins 1 Github Branch Source 2023-12-10 6.8 MEDIUM 6.3 MEDIUM
GitHub Branch Source Plugin connects to a user-specified GitHub API URL (e.g. GitHub Enterprise) as part of form validation and completion (e.g. to verify Scan Credentials are correct). This functionality improperly checked permissions, allowing any user with Overall/Read access to Jenkins to connect to any web server and send credentials with a known ID, thereby possibly capturing them. Additionally, this functionality did not require POST requests be used, thereby allowing the above to be performed without direct access to Jenkins via Cross-Site Request Forgery.