CVE-2021-21654: Missing Authorization in Jenkins P4 plugin
Summary
CVE-2021-21654: Missing Authorization in Jenkins P4 plugin. Affects org.jenkins-ci.plugins:p4 versions < 1.11.5. Fixed in 1.11.5. 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 P4 Plugin is a plugin for the Jenkins automation server that integrates with the Perforce version control system. It allows users to configure and manage Perforce connections within Jenkins, enabling seamless integration of Perforce functionality into Jenkins workflows. The plugin provides various features such as syncing files, submitting changes, and managing Perforce clients. However, versions 1.11.4 and earlier of the plugin suffer from a vulnerability that allows attackers with Overall/Read permission to connect to an attacker-specified Perforce server using an attacker-specified username and password.
Vulnerability Detail
The vulnerability in the Jenkins P4 Plugin arises from the lack of proper permission checks in multiple HTTP endpoints. This oversight enables attackers with Overall/Read permission to establish connections to arbitrary Perforce servers using their chosen credentials. By exploiting this vulnerability, an attacker can gain unauthorized access to Perforce repositories, potentially leading to unauthorized code modifications, data leaks, or other malicious activities. The vulnerability has a CVSS score of 4.3, indicating a moderate severity level.
How To Fix
Latest published version: 1.18.1 as of 22 Oct 2026
Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.
If you need the minimum change
1.11.5
This is the first release that contains the fix.
Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Workaround
As a temporary workaround, organizations can restrict access to the affected HTTP endpoints by adjusting the permissions of the Jenkins instance. Specifically, the Overall/Read permission should be limited to trusted users only. This can be achieved by modifying the Jenkins configuration or using a plugin that provides more granular access control. However, applying the workaround is not a permanent solution, and upgrading to the latest version of the Jenkins P4 Plugin is strongly recommended.
Conclusion
The Jenkins P4 Plugin versions 1.11.4 and earlier suffer from a missing authorization vulnerability that allows attackers with Overall/Read permission to connect to arbitrary Perforce servers using their chosen credentials. To mitigate this vulnerability, it is crucial to upgrade to version 1.11.5 or later of the plugin, which includes the necessary permission checks. Applying the recommended fixes ensures that only authorized users with the appropriate permissions can access Perforce servers. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for org.jenkins-ci.plugins:p4 →
FAQ
The vulnerability allows attackers with Overall/Read permission to connect to arbitrary Perforce servers using their chosen credentials. This unauthorized access can lead to unauthorized code modifications, data leaks, or other malicious activities.
Organizations using Jenkins P4 Plugin versions 1.11.4 and earlier are affected by this vulnerability.
At the time of this advisory, there are no known public exploits specifically targeting this vulnerability. However, it is advisable to apply the recommended fixes as soon as possible to mitigate any potential risks.
Yes, this vulnerability can be exploited remotely by attackers with Overall/Read permission.
Yes, the CVSS score for this vulnerability is 4.3, indicating a moderate severity level.
Related vulnerabilities
Recent vulnerabilities recorded for org.jenkins-ci.plugins:p4.
