org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source: Incorrect Permission Assignment for Critical Resource in Jenkins Bitbucket Branch…
It touches something Phylax follows. No evidence of use yet.
Does it affect what I run?
Checked in your browser. The version you type is not sent anywhere.
Who is affected
- org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source (Maven): from 726.v7e6f53de133c, before 746.v350d2781c184
- org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source (Maven): from 720.vbe985dd73d66, before 725.vd9f8be0fa250
- org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source (Maven): from 2.9.8, before 2.9.11.2
- org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source (Maven): every version, before 2.9.7.2
The fix
org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source (Maven) fixed in 746.v350d2781c184
mavenmvn versions:use-dep-version -Dincludes=org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source -DdepVersion=746.v350d2781c184 -DforceVersion=trueCheck what is installedmvn dependency:tree -Dincludes=org.jenkins-ci.plugins:cloudbees-bitbucket-branch-sourcePaste into Cursor, Lovable or Claude CodeUpgrade the Maven dependency org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source to 746.v350d2781c184 or the nearest later release, to fix CVE-2022-20618. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source (Maven) fixed in 725.vd9f8be0fa250
mavenmvn versions:use-dep-version -Dincludes=org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source -DdepVersion=725.vd9f8be0fa250 -DforceVersion=trueCheck what is installedmvn dependency:tree -Dincludes=org.jenkins-ci.plugins:cloudbees-bitbucket-branch-sourcePaste into Cursor, Lovable or Claude CodeUpgrade the Maven dependency org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source to 725.vd9f8be0fa250 or the nearest later release, to fix CVE-2022-20618. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source (Maven) fixed in 2.9.11.2
mavenmvn versions:use-dep-version -Dincludes=org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source -DdepVersion=2.9.11.2 -DforceVersion=trueCheck what is installedmvn dependency:tree -Dincludes=org.jenkins-ci.plugins:cloudbees-bitbucket-branch-sourcePaste into Cursor, Lovable or Claude CodeUpgrade the Maven dependency org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source to 2.9.11.2 or the nearest later release, to fix CVE-2022-20618. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source (Maven) fixed in 2.9.7.2
mavenmvn versions:use-dep-version -Dincludes=org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source -DdepVersion=2.9.7.2 -DforceVersion=trueCheck what is installedmvn dependency:tree -Dincludes=org.jenkins-ci.plugins:cloudbees-bitbucket-branch-sourcePaste into Cursor, Lovable or Claude CodeUpgrade the Maven dependency org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source to 2.9.7.2 or the nearest later release, to fix CVE-2022-20618. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.
Fix commands generated from the advisory's versions. No model wrote them.
In plain words
Brief pending: here are the facts and the fix. The explanation in plain words follows when it has been written and checked.
Evidence
No evidence that it is being used, or can be. It is listed because of what it affects.
Timeline
- First published here, as "For your digest".