CVE-2020-2227: Stored XSS vulnerability in Jenkins Deployer Framework Plugin
Summary
CVE-2020-2227: Stored XSS vulnerability in Jenkins Deployer Framework Plugin. Affects org.jenkins-ci.plugins:deployer-framework versions < 1.3. Fixed in 1.3. 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 Deployer Framework Plugin is a framework plugin that enables other plugins to provide a mechanism for deploying artifacts. It allows users to deploy artifacts to various locations. The plugin versions up to 1.2 are affected by a stored cross-site scripting (XSS) vulnerability. This vulnerability arises due to the lack of URL escaping in the build home page, allowing malicious users to inject arbitrary scripts. The Jenkins security team has not identified any exploitable implementations of this vulnerability.
Vulnerability Detail
The stored XSS vulnerability in the Jenkins Deployer Framework Plugin (CVE-2020-2227) allows authenticated users with the ability to provide a location to inject malicious scripts. This vulnerability can be exploited by crafting a URL that contains the malicious script and tricking another user into visiting the affected build home page. The impact of this vulnerability depends on the specific implementation using the Deployer Framework Plugin. It could lead to unauthorized access, data theft, or other malicious activities.
How To Fix
Minimum fixed version
1.3
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
There is no known workaround for this vulnerability. It is advised to upgrade to the fixed version of the plugin as soon as possible.
Conclusion
The Jenkins Deployer Framework Plugin versions up to 1.2 are affected by a stored XSS vulnerability. Upgrading to version 1.3 or later is the recommended solution. This will escape the URL and prevent the injection of malicious scripts. It is important to promptly address this vulnerability to mitigate the risk of unauthorized access and data theft. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for org.jenkins-ci.plugins:deployer-framework →
FAQ
The impact of this vulnerability depends on the specific implementation using the Deployer Framework Plugin. It could lead to unauthorized access, data theft, or other malicious activities.
The Jenkins security team is not aware of any exploitable implementations of this vulnerability.
You can use Vulert's playground (https://vulert.com/scanner) to check if your Jenkins installation is affected by this vulnerability. Vulert monitors and alerts in real-time for open-source vulnerabilities in software using just the pom.xml file.
Yes, upgrading to Deployer Framework Plugin version 1.3 or later fixes this vulnerability.
There is no known workaround for this vulnerability. It is highly recommended to upgrade to the fixed version of the plugin.
Related vulnerabilities
Recent vulnerabilities recorded for org.jenkins-ci.plugins:deployer-framework.
