VsphereApplication · Jenkins
CVE-2018-1000151
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Jenkins vSphere Plugin versions 2.16 and older contains a vulnerability in VSphere.java that disables SSL/TLS certificate validation by default. This allows man-in-the-middle attackers to intercept and modify communications between Jenkins and the vSphere server by presenting invalid or forged certificates, compromising confidentiality and integrity of data in transit.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
VsphereApplication
<= 2.16CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check the installed vSphere Plugin versionIn Jenkins, go to Manage Jenkins > Manage Plugins > Installed tab, or check the plugin's .hpi file in $JENKINS_HOME/plugins for the version manifestAffected if The installed version is 2.16 or older (<= 2.16)
-
Verify SSL/TLS certificate validation settingCheck the vSphere cloud configuration in Jenkins (Manage Jenkins > Configure System > vSphere) or inspect the configuration XML file in $JENKINS_HOME/com.demondevelop.vsphere.xml for SSL-related settingsAffected if The configuration shows SSL certificate validation is disabled or the setting is not present (defaults to disabled in affected versions)
-
Inspect the VSphere.java plugin fileLocate VSphere.java in the plugin jar at $JENKINS_HOME/plugins/vsphere/*.jar, decompile or examine the source code for the SSL validation initialization logicAffected if The code contains logic that defaults SSL verification to false or skips certificate validation checks by default
You are affected if the vSphere Plugin version is 2.16 or older AND SSL certificate validation is disabled or not explicitly enabled in the configuration.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade the Jenkins vSphere Plugin to version 2.17 or later which fixes the certificate validation issue, or ensure proper certificate validation is enabled in the plugin configuration if a patched version is available.
Fix this in Vsphere
Scoped from the published advisory
- Consultation4.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-1000151 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2018-1000151 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data