CVE-2022-20618

Incorrect Permission Assignment for Critical Resource 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 perform permission checks in several HTTP endpoints.

This allows attackers with Overall/Read access to enumerate credentials IDs of credentials stored in Jenkins. Those can be used as part of an attack to capture the credentials using another vulnerability.

An enumeration of credentials IDs in Bitbucket Branch Source Plugin 746.v350d2781c184, 725.vd9f8be0fa250, 2.9.11.2, and 2.9.7.2 requires the appropriate permissions.

A file, directory, or other resource is assigned permissions that allow broader access than intended. Typical impact: unauthorized read, modification, or execution of the resource.

CVE-2022-20618 has a CVSS score of 4.3 (Medium). The vector is network-reachable, low privileges required, and no user interaction. 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.

Kodem intelligence

Already deployed Kodem?

1. What is CVE-2022-20618? CVE-2022-20618 is a medium-severity incorrect permission assignment for critical resource 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 file, directory, or other resource is assigned permissions that allow broader access than intended.
2. How severe is CVE-2022-20618? CVE-2022-20618 has a CVSS score of 4.3 (Medium). 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.
3. Which versions of org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source are affected by CVE-2022-20618? org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source (maven) versions >= 726.v7e6f53de133c, < 746.v350d2781c184 is affected.
4. Is there a fix for CVE-2022-20618? Yes. CVE-2022-20618 is fixed in 746.v350d2781c184, 725.vd9f8be0fa250, 2.9.11.2, 2.9.7.2. Upgrade to this version or later.
5. Is CVE-2022-20618 exploitable, and should I be worried? Whether CVE-2022-20618 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
6. What actually determines whether CVE-2022-20618 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.
7. How do I fix CVE-2022-20618?
   • Upgrade org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source to 746.v350d2781c184 or later
   • Upgrade org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source to 725.vd9f8be0fa250 or later
   • Upgrade org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source to 2.9.11.2 or later
   • Upgrade org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source to 2.9.7.2 or later

Other vulnerabilities in org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source