CVE-2020-2116: CSRF vulnerability in Pipeline GitHub Notify Step Plugin allows capturing credentials
Summary
CVE-2020-2116: CSRF vulnerability in Pipeline GitHub Notify Step Plugin allows capturing credentials. Affects org.jenkins-ci.plugins:pipeline-githubnotify-step versions < 1.0.5. Fixed in 1.0.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 Pipeline GitHub Notify Step Plugin is a Jenkins plugin that allows users to send notifications to GitHub repositories during a Jenkins pipeline. It provides functionality to notify GitHub about the status of a build or any other relevant information. The plugin is widely used in Jenkins pipelines for integrating with GitHub. However, versions 1.0.4 and earlier of the plugin are vulnerable to a cross-site request forgery (CSRF) attack.
Vulnerability Detail
The CSRF vulnerability in the Pipeline GitHub Notify Step Plugin allows attackers to connect to a URL of their choice using credentials obtained through another method. By exploiting this vulnerability, an attacker can capture credentials stored in Jenkins. This can lead to unauthorized access to sensitive information or actions within the Jenkins environment. The vulnerability has a CVSS score of 7.1, indicating a high severity level.
How To Fix
Minimum fixed version
1.0.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
There is no known workaround for this vulnerability. It is essential to apply the recommended fix by upgrading the plugin to the latest version.
Conclusion
The CSRF vulnerability in the Pipeline GitHub Notify Step Plugin exposes Jenkins installations to the risk of credential capture and unauthorized access. It is crucial to upgrade the plugin to version 1.0.5 or later to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for org.jenkins-ci.plugins:pipeline-githubnotify-step →
FAQ
The vulnerability allows attackers to capture credentials stored in Jenkins, potentially leading to unauthorized access and misuse of sensitive information.
You can use the Vulert Playground at Vulert 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 report. However, it is crucial to apply the recommended fix to mitigate the risk.
Yes, this vulnerability can be exploited remotely by an attacker who can trick a user with Jenkins access to visit a malicious website or click on a specially crafted link.
There is no evidence of active exploitation of this vulnerability at the time of this report. However, it is recommended to apply the fix as soon as possible to prevent any potential attacks.
Related vulnerabilities
Recent vulnerabilities recorded for org.jenkins-ci.plugins:pipeline-githubnotify-step.
