CVE-2022-36904: Jenkins Repository Connector Plugin - Permission Check Bypass
Summary
CVE-2022-36904: Jenkins Repository Connector Plugin 2.2.0 and earlier does not perform a permission check in a method implementing form validation. Affects org.jenkins-ci.plugins:repository-connector versions < 2.2.0. No fix is published. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
The Jenkins Repository Connector Plugin is a Maven plugin that allows Jenkins to interact with external repositories. It provides functionality for downloading artifacts from repositories and uploading artifacts to repositories. This plugin is widely used in Jenkins environments to manage dependencies and artifacts. However, versions 2.2.0 and earlier of the plugin are vulnerable to a permission check bypass.
Vulnerability Detail
The vulnerability in the Jenkins Repository Connector Plugin allows attackers with Overall/Read permission to check for the existence of a file on the Jenkins controller file system. This is due to a lack of permission check in a method implementing form validation. By exploiting this vulnerability, an attacker can determine the presence of arbitrary files on the system, potentially leading to further attacks or unauthorized access.
How To Fix
No fixed version is published for this vulnerability.
Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →
Workaround
There is no known workaround for this vulnerability. It is necessary to apply the fix by upgrading to a secure version of the Jenkins Repository Connector Plugin.
Conclusion
The Jenkins Repository Connector Plugin versions 2.2.0 and earlier are vulnerable to a permission check bypass, allowing attackers with Overall/Read permission to check for the existence of arbitrary files on the Jenkins controller file system. To mitigate this vulnerability, it is crucial to upgrade to a fixed version of the plugin (2.2.1 or later) and review user permissions. For further assistance with vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for org.jenkins-ci.plugins:repository-connector →
FAQ
This vulnerability allows attackers to check for the existence of arbitrary files on the Jenkins controller file system. While it does not directly grant access to the contents of the files, it can provide valuable information for further attacks or unauthorized access.
Users of Jenkins Repository Connector Plugin versions 2.2.0 and earlier are affected by this vulnerability.
There are no known public exploits for this vulnerability at the time of this report. However, it is advisable to apply the fix as soon as possible to mitigate the risk.
You can use the Vulert Playground (https://vulert.com/scanner) to check if your Jenkins installation is affected by this vulnerability. Simply provide your pom.xml file, and Vulert will analyze it for any open-source vulnerabilities, including this one.
For more information about this vulnerability, you can refer to the GitHub Security Advisory GHSA-fjpq-f574-jc45 (https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2022/07/GHSA-fjpq-f574-jc45/GHSA-fjpq-f574-jc45.json).
Related vulnerabilities
Recent vulnerabilities recorded for org.jenkins-ci.plugins:repository-connector.
