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

Medium 4.3 Published Updated

Attackers with read access can enumerate stored credential IDs due to missing permission checks in the Jenkins Bitbucket Branch Source Plugin.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

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

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.

PackageAffectedFixed in
org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source MavenAll versions2.9.7.2
org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source MavenAll versions2.9.7.2
org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source MavenFrom 2.9.82.9.11.2
org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source MavenFrom 2.9.82.9.11.2
org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source MavenFrom 720.vbe985dd73d66725.vd9f8be0fa250
org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source MavenFrom 720.vbe985dd73d66725.vd9f8be0fa250
2 more packages
org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source MavenFrom 726.v7e6f53de133c746.v350d2781c184
org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source MavenFrom 726.v7e6f53de133c746.v350d2781c184

Products include 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.

Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.

Is CVE-2022-20618 being exploited?

There is no known exploitation of CVE-2022-20618 in the wild and no public exploit code.

Sources

Also known as GHSA-w2mh-6xj5-f77f.

Is CVE-2022-20618 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free