Summary
Cross-Site Request Forgery in Jenkins Bitbucket Branch Source Plugin
Jenkins Bitbucket Branch Source Plugin prior to 746.v350d2781c184, 725.vd9f8be0fa250, 2.9.11.2, and 2.9.7.2 does not require POST requests for an HTTP endpoint, resulting in a cross-site request forgery (CSRF) vulnerability.
This allows attackers with Overall/Read access to connect to an attacker-specified URL using attacker-specified credentials IDs obtained through another method, capturing credentials stored in Jenkins.
Bitbucket Branch Source Plugin 746.v350d2781c184, 725.vd9f8be0fa250, 2.9.11.2, and 2.9.7.2 requires POST requests for the affected HTTP endpoint.
Impact
A victim's authenticated browser session is used to submit forged requests to an application that cannot distinguish them from legitimate ones. Typical impact: state-changing actions performed as the victim without their consent.
CVE-2022-20619 has a CVSS score of 7.1 (High). The vector is network-reachable, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (746.v350d2781c184, 725.vd9f8be0fa250, 2.9.11.2, 2.9.7.2); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source to 746.v350d2781c184 or later; org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source to 725.vd9f8be0fa250 or later; org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source to 2.9.11.2 or later; org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source to 2.9.7.2 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2022-20619? CVE-2022-20619 is a high-severity cross-site request forgery (CSRF) vulnerability in org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source (maven), affecting versions >= 726.v7e6f53de133c, < 746.v350d2781c184. It is fixed in 746.v350d2781c184, 725.vd9f8be0fa250, 2.9.11.2, 2.9.7.2. A victim's authenticated browser session is used to submit forged requests to an application that cannot distinguish them from legitimate ones.
- How severe is CVE-2022-20619? CVE-2022-20619 has a CVSS score of 7.1 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source are affected by CVE-2022-20619? org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source (maven) versions >= 726.v7e6f53de133c, < 746.v350d2781c184 is affected.
- Is there a fix for CVE-2022-20619? Yes. CVE-2022-20619 is fixed in 746.v350d2781c184, 725.vd9f8be0fa250, 2.9.11.2, 2.9.7.2. Upgrade to this version or later.
- Is CVE-2022-20619 exploitable, and should I be worried? Whether CVE-2022-20619 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2022-20619 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2022-20619?
- Upgrade
org.jenkins-ci.plugins:cloudbees-bitbucket-branch-sourceto 746.v350d2781c184 or later - Upgrade
org.jenkins-ci.plugins:cloudbees-bitbucket-branch-sourceto 725.vd9f8be0fa250 or later - Upgrade
org.jenkins-ci.plugins:cloudbees-bitbucket-branch-sourceto 2.9.11.2 or later - Upgrade
org.jenkins-ci.plugins:cloudbees-bitbucket-branch-sourceto 2.9.7.2 or later
- Upgrade