# CVE-2022-20618: Incorrect Permission Assignment for Critical Resource in Jenkins Bitbucket Branch Source Plugin > Attackers with read access can enumerate stored credential IDs due to missing permission checks in the Jenkins Bitbucket Branch Source Plugin. - **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 12 Jan 2022 - **Updated:** 3 Aug 2024 - **Also known as:** GHSA-w2mh-6xj5-f77f ## What is CVE-2022-20618? CVE-2022-20618 is a medium-severity missing authorization vulnerability in Jenkins Bitbucket Branch Source Plugin, published on 12 Jan 2022. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description A missing permission check in Jenkins Bitbucket Branch Source Plugin 737.vdf9dc06105be and earlier allows attackers with Overall/Read access to enumerate credentials IDs of credentials stored in Jenkins. Weakness: CWE-862 (Missing Authorization) ## Which versions are affected by CVE-2022-20618? 8 open source packages ship an affected version, including org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source` | Maven | All versions | 2.9.7.2 | | `org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source` | Maven | All versions | 2.9.7.2 | | `org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source` | Maven | From 2.9.8 | 2.9.11.2 | | `org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source` | Maven | From 2.9.8 | 2.9.11.2 | | `org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source` | Maven | From 720.vbe985dd73d66 | 725.vd9f8be0fa250 | | `org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source` | Maven | From 720.vbe985dd73d66 | 725.vd9f8be0fa250 | | `org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source` | Maven | From 726.v7e6f53de133c | 746.v350d2781c184 | | `org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source` | Maven | From 726.v7e6f53de133c | 746.v350d2781c184 | Products: Jenkins Bitbucket Branch Source. ## How do I fix CVE-2022-20618? Upgrade org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source to a fixed version for your release line: 2.9.7.2, 2.9.11.2, 725.vd9f8be0fa250 or 746.v350d2781c184. ## Is CVE-2022-20618 being exploited? There is no known exploitation of CVE-2022-20618 in the wild and no public exploit code. ## Other vulnerabilities in Jenkins Bitbucket Branch Source Plugin - [CVE-2022-20619](https://insights.sbomify.com/CVE-2022-20619/): Cross-Site Request Forgery in Jenkins Bitbucket Branch Source Plugin (high 7.1) - [CVE-2024-28152](https://insights.sbomify.com/CVE-2024-28152/): Jenkins Bitbucket Branch Source Plugin has incorrect trust policy behavior for pull requests (medium 6.3) - [CVE-2024-39460](https://insights.sbomify.com/CVE-2024-39460/): Bitbucket OAuth access token exposed in the build log by Bitbucket Branch Source Plugin (medium 4.3) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2022-20618 and fix it if it is affected. What it is: CVE-2022-20618 is a medium-severity missing authorization vulnerability in Jenkins Bitbucket Branch Source Plugin, published on 12 Jan 2022. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2022-20618 in the wild and no public exploit code. Affected packages and fixed versions: - org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source (Maven): affected all versions; fixed in 2.9.7.2 - org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source (Maven): affected all versions; fixed in 2.9.7.2 - org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source (Maven): affected from 2.9.8; fixed in 2.9.11.2 - org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source (Maven): affected from 2.9.8; fixed in 2.9.11.2 - org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source (Maven): affected from 720.vbe985dd73d66; fixed in 725.vd9f8be0fa250 - org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source (Maven): affected from 720.vbe985dd73d66; fixed in 725.vd9f8be0fa250 - org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source (Maven): affected from 726.v7e6f53de133c; fixed in 746.v350d2781c184 - org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source (Maven): affected from 726.v7e6f53de133c; fixed in 746.v350d2781c184 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2022-20618/ (Markdown: https://insights.sbomify.com/CVE-2022-20618/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2022-20618 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-20618 - OSV: https://osv.dev/vulnerability/CVE-2022-20618 --- From sbomify Insights: https://insights.sbomify.com/CVE-2022-20618/ Summaries are generated and may contain mistakes; the official description above is the record.