CVE-2018-1000182: Server-Side Request Forgery in Jenkins Git Plugin
Summary
CVE-2018-1000182: Server-Side Request Forgery in Jenkins Git Plugin. Affects org.jenkins-ci.plugins:git versions < 3.9.1. Fixed in 3.9.1. 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 Git Plugin is a popular plugin for the Jenkins automation server that allows users to integrate Git repositories into their Jenkins pipelines. It provides functionality for cloning, fetching, and pushing to Git repositories. This vulnerability affects versions 3.9.0 and older of the plugin.
Vulnerability Detail
A server-side request forgery vulnerability exists in Jenkins Git Plugin 3.9.0 and older. The vulnerability is present in several classes, including AssemblaWeb.java, GitBlitRepositoryBrowser.java, Gitiles.java, TFS2013GitRepositoryBrowser.java, and ViewGitWeb.java. Attackers with Overall/Read access can exploit this vulnerability to cause Jenkins to send a GET request to a specified URL. This can lead to various security issues, such as information disclosure, unauthorized access to internal resources, and potential remote code execution.
How To Fix
Minimum fixed version
3.9.1
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
If upgrading to the latest version of the Jenkins Git Plugin is not immediately feasible, users can implement a workaround by restricting access to the Jenkins server. This can be done by configuring network firewalls or access control lists (ACLs) to block external requests to the Jenkins server. Additionally, users can review and modify the permissions of Jenkins users with Overall/Read access to minimize the risk of exploitation.
Conclusion
The server-side request forgery vulnerability in Jenkins Git Plugin 3.9.0 and older poses a risk of unauthorized access, information disclosure, and potential remote code execution. It is crucial for users to upgrade to version 3.9.1 or later of the plugin to mitigate this vulnerability. If immediate upgrade is not possible, implementing access restrictions and reviewing user permissions can provide temporary mitigation. For further support and assistance in vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for org.jenkins-ci.plugins:git →
FAQ
This vulnerability can allow attackers to manipulate Jenkins to send unauthorized GET requests to external URLs, potentially leading to information disclosure, unauthorized access, and remote code execution.
Users of Jenkins Git Plugin versions 3.9.0 and older are affected by this vulnerability.
There are no known public exploits specifically targeting this vulnerability at the time of this report. However, it is important to promptly apply the recommended fix to mitigate the risk of exploitation.
Yes, this vulnerability can be exploited remotely by attackers with Overall/Read access to the Jenkins server.
Yes, the CVSS score for this vulnerability is 6.4, indicating a moderate severity level.
Related vulnerabilities
Recent vulnerabilities recorded for org.jenkins-ci.plugins:git.
