CVE-2022-20618 — cloudbees-bitbucket-branc…
MEDIUMFix: jenkinsci/bitbucket-branch-source-plugin@467ed6cCVE-2022-20618 is a medium-severity (CVSS 4.3) CWE-862 vulnerability in org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source. A fix is available for org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source — see the affected versions and patch details below.
Incorrect Permission Assignment for Critical Resource in Jenkins Bitbucket Branch Source Plugin
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source☕org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source☕org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source☕org.jenkins-ci.plugins:cloudbees-bitbucket-branch-sourceReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source | ≥ 726.v7e6f53de133c&&< 746.v350d2781c184 | 746.v350d2781c184org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source:746.v350d2781c184 |
| ☕Maven | org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source | ≥ 720.vbe985dd73d66&&< 725.vd9f8be0fa250 | 725.vd9f8be0fa250org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source:725.vd9f8be0fa250 |
| ☕Maven | org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source | ≥ 2.9.8&&< 2.9.11.2 | 2.9.11.2org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source:2.9.11.2 |
| ☕Maven | org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source | all versions | 2.9.7.2org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source:2.9.7.2 |
Affected Products
bitbucket branch sourcejenkinsDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source to 746.v350d2781c184 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-20618 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.
Frequently Asked Questions
Is CVE-2022-20618 in your dependencies?
Find it across Maven, including transitive dependencies.