CVE-2018-1000151: Jenkins vSphere Plugin SSL/TLS Certificate Validation Bypass
Summary
CVE-2018-1000151: Jenkins vSphere Plugin disables SSL/TLS certificate validation by default. Affects org.jenkins-ci.plugins:vsphere-cloud versions < 2.17. Fixed in 2.17. 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 vSphere Plugin is a Maven package (org.jenkins-ci.plugins:vsphere-cloud) that provides integration between Jenkins and VMware vSphere. It allows users to dynamically provision Jenkins agents on vSphere virtual machines. The plugin is widely used in continuous integration and deployment workflows.
Vulnerability Detail
The vSphere Plugin version 2.16 and older contain a vulnerability in the VSphere.java file. By default, SSL/TLS certificate validation is disabled, leaving the plugin susceptible to man-in-the-middle attacks. An attacker can intercept and modify communication between Jenkins and vSphere, potentially leading to unauthorized access, data tampering, or other malicious activities. The vulnerability has a CVSS score of 5.6 (Medium severity).
How To Fix
Minimum fixed version
2.17
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, users can manually enable SSL/TLS certificate validation in the vSphere Plugin configuration. This can be done by accessing the Jenkins global configuration, navigating to the vSphere Cloud section, and checking the 'Enable SSL certificate validation' option. However, it is strongly recommended to upgrade to the latest version of the plugin for a permanent fix.
Conclusion
The Jenkins vSphere Plugin version 2.16 and older are vulnerable to a man-in-the-middle attack due to disabled SSL/TLS certificate validation. Users should upgrade to version 2.17 or newer to mitigate this vulnerability. Alternatively, a temporary workaround is available by enabling SSL/TLS certificate validation manually. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for org.jenkins-ci.plugins:vsphere-cloud →
FAQ
This vulnerability allows an attacker to intercept and modify communication between Jenkins and vSphere, potentially leading to unauthorized access, data tampering, or other malicious activities.
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.
Yes, the vulnerability can be fixed by upgrading to vSphere Plugin version 2.17 or newer. The updated version enables SSL/TLS certificate validation by default.
Yes, a temporary workaround is available. Users can manually enable SSL/TLS certificate validation in the vSphere Plugin configuration. However, it is recommended to upgrade to the latest version for a permanent fix.
For more information about this vulnerability, you can refer to the CVE-2018-1000151 entry or contact the Jenkins community for assistance.
Related vulnerabilities
Recent vulnerabilities recorded for org.jenkins-ci.plugins:vsphere-cloud.
