CVE-2022-20618: Incorrect Permission Assignment for Critical Resource in Jenkins Bitbucket Branch Source Plugin

CVE-2022-20618 · Severity: low · CVSS 3.1 · Published 2022-01-13

Incorrect Permission Assignment for Critical Resource in Jenkins Bitbucket Branch Source Plugin

Technologies: org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source (Maven). Vendors: Maven.

Quick answers

Is CVE-2022-20618 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2022-20618 being exploited in the wild.
How severe is CVE-2022-20618?
Low severity, with a CVSS score of 3.1, published 13 January 2022.
Which products and versions are affected?
org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source (Maven) ECOSYSTEM:introduced=726.v7e6f53de133c,fixed=746.v350d2781c184.
Is there a fix for CVE-2022-20618?
Yes. org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source (Maven): upgrade to 746.v350d2781c184 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2022-20618?
Check whether you run org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source (Maven): upgrade to 746.v350d2781c184 or later
    # set org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source to 746.v350d2781c184 in your pom.xml or build.gradle

Affected products

  • org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source (Maven) ECOSYSTEM:introduced=726.v7e6f53de133c,fixed=746.v350d2781c184

Identifiers

  • CVE-2022-20618
  • GHSA-w2mh-6xj5-f77f

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.