CVE-2020-2237: CSRF vulnerability in Jenkins Flaky Test Handler Plugin
Summary
CVE-2020-2237: CSRF vulnerability in Jenkins Flaky Test Handler Plugin. Affects org.jenkins-ci.plugins:flaky-test-handler versions < 1.1.0. Fixed in 1.1.0. 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 Flaky Test Handler Plugin is a Maven-based plugin that is used to handle flaky tests in Jenkins projects. It provides features to identify and manage flaky tests, allowing developers to deflake builds and improve test reliability. The plugin is widely used in Jenkins environments to ensure the stability of software projects.
Vulnerability Detail
The Flaky Test Handler Plugin version 1.0.4 and earlier is vulnerable to a cross-site request forgery (CSRF) attack. The plugin does not enforce the use of POST requests for the 'Deflake this build' feature, which allows an attacker to forge a request and rebuild a project at a previous git revision where the tests were failing. This vulnerability can be exploited by an attacker to manipulate the test results and potentially introduce malicious code into the project.
How To Fix
Latest published version: 1.3.172.v35b_30de7fa_5b_ as of 23 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.1.0
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 essential to upgrade to the fixed version of the Flaky Test Handler Plugin to mitigate the risk.
Conclusion
The CSRF vulnerability in the Jenkins Flaky Test Handler Plugin can allow attackers to manipulate test results and potentially introduce malicious code into Jenkins projects. It is crucial to upgrade to the fixed version of the plugin (1.1.0 or later) to mitigate the risk. Users should update their Jenkins installation and ensure the updated plugin is installed. For further support on vulnerability remediation, contact DevNack.com.
See every vulnerability recorded for org.jenkins-ci.plugins:flaky-test-handler →
FAQ
This vulnerability allows attackers to manipulate test results and potentially introduce malicious code into Jenkins projects. It can undermine the integrity and reliability of software builds.
You can use the Vulert 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, using just the pom.xml file.
There are no known public exploits for this vulnerability at the time of this advisory. However, it is crucial to apply the recommended fix to prevent potential attacks.
Yes, this vulnerability can be exploited remotely by an attacker who can trick a user with Jenkins access into visiting a malicious website or clicking on a crafted link.
There is no evidence of active exploitation of this vulnerability at the time of this advisory. However, it is recommended to apply the fix as soon as possible to mitigate the risk.
Related vulnerabilities
Recent vulnerabilities recorded for org.jenkins-ci.plugins:flaky-test-handler.
