GitHub Advisoryadvisory · Maven

GHSA-8xwj-2wgh-gprh Lack of authentication mechanism in Jenkins Git Plugin webhook

MEDIUM Published 2022-07-28 Modified 2022-12-12 Official page ↗
Aliases
CVE-2022-36882
Ecosystem
Maven
Packages
org.jenkins-ci.plugins:git
Severity
Moderate
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
Weaknesses
CWE-352
Reviewed
2022-08-10

Affected packages

• Maven org.jenkins-ci.plugins:git: < 4.11.4 → fixed in 4.11.4

Description

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. This webhook endpoint does not require POST requests, resulting in a cross-site request forgery (CSRF) vulnerability. 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.

Related

Alias · CVE (1)

  • CVE-2022-36882 A cross-site request forgery (CSRF) vulnerability in Jenkins Git Plugin 4.11.3 and earlier allows attackers to trigger builds of jobs… vulnerability

Weakness · CWE (1)

  • CWE-352 Cross-Site Request Forgery weakness

References