Jenkins vSphere Plugin disables SSL/TLS certificate validation by default

published 2018-04-05 8y ago modified 2026-06-17 4mo ago also GHSA-vq7p-f4fv-rr5x , EUVD-2022-5407

cvss: 5.6; version 3.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 0.4%; EPSS 0.4% chance of exploitation in 30 days, percentile 36%
public exploits: 0; none known

A man in the middle vulnerability exists in Jenkins vSphere Plugin 2.16 and older in VSphere.java that disables SSL/TLS certificate validation by default.

Patch / fix

fixed in 1 links 1

maven org.jenkins-ci.plugins:vsphere-cloud 2.17

github.com/jenkinsci/vsphere-cloud-plugin@f0fb143 commit

Is CVE-2018-1000151 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.42% chance of exploitation in the next 30 days, higher than 36% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	3.0	5.6	CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L
NVD	2.0	6.8	AV:N/AC:M/Au:N/C:P/I:P/A:P
GitHub	3.0	5.6	CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L

Affected packages

ecosystem	package	affected	fixed in
maven	org.jenkins-ci.plugins:vsphere-cloud	<2.17	2.17

Classification

Weakness

CWE-295 Improper Certificate Validation

References

github.com /jenkinsci/vsphere-cloud-plugin/commit/f0fb143af340c7529dd9e50f5514334756019356
web
jenkins.io /security/advisory/2018-03-26/#SECURITY-504
web, vendor-advisory
nvd.nist.gov /vuln/detail/CVE-2018-1000151
advisory
github.com /jenkinsci/vsphere-cloud-plugin
package

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.