dbcve.org
VsphereApplication · Jenkins

CVE-2018-1000153

HIGH · 8.8 CVSS v3.0 Published 2018-04-05
Fix available
A fix is available. Upgrade to after 2.16 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 · unedited
A cross-site request forgery vulnerability exists in Jenkins vSphere Plugin 2.16 and older in Clone.java, CloudSelectorParameter.java, ConvertToTemplate.java, ConvertToVm.java, Delete.java, DeleteSnapshot.java, Deploy.java, ExposeGuestInfo.java, FolderVSphereCloudProperty.java, PowerOff.java, PowerOn.java, Reconfigure.java, Rename.java, RenameSnapshot.java, RevertToSnapshot.java, SuspendVm.java, TakeSnapshot.java, VSphereBuildStepContainer.java, vSphereCloudProvisionedSlave.java, vSphereCloudSlave.java, vSphereCloudSlaveTemplate.java, VSphereConnectionConfig.java, vSphereStep.java that allows attackers to perform form validation related actions, including sending numerous requests to the configured vSphere server, potentially resulting in denial of service, or send credentials stored in Jenkins with known ID to an attacker-specified server ("test connection").

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 confidence

CSRF vulnerability in Jenkins vSphere Plugin 2.16 and older allows attackers to trigger form validation actions without user consent, including sending repeated requests to the configured vSphere server (potential DoS) and exfiltrating Jenkins-stored credentials to attacker-controlled servers via the 'test connection' feature.

MitigationUpdate Jenkins vSphere Plugin to version newer than 2.16, which should include CSRF protection tokens. Additionally, ensure Jenkins global security settings enforce CSRF protection.

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
Affected:<= 2.16

CVSS 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
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate the vSphere Plugin installation
    Check the Jenkins plugin directory (typically $JENKINS_HOME/plugins/) for a folder named 'vsphere' or 'vSphere', or access Manage Jenkins > Manage Plugins > Installed tab and search for 'vSphere' or 'vsphere'.
    Affected if The plugin folder or entry exists in Jenkins.
  2. Determine the installed vSphere Plugin version
    If using the web UI, click on the vSphere Plugin entry in the Installed plugins list to view its version. If using the filesystem, check the $JENKINS_HOME/plugins/vsphere/META-INF/MANIFEST.MF file for the 'Plugin-Version' attribute, or examine the .jpi file name if it includes a version suffix.
    Affected if The plugin is installed and a version number is displayed or found.
  3. Compare your version to the affected range
    Review the version identified in step 2 and compare it numerically to version 2.16. Note that versions like 2.16, 2.15, 2.14, 2.0, 1.x, and any version number lower than or equal to 2.16 are within the vulnerable range.
    Affected if The installed version is 2.16 or any earlier version (2.16, 2.15, 2.14, 2.0, 1.x, etc.).
  4. Verify the test connection feature is accessible
    Navigate to Jenkins > Manage Jenkins > Configure System and locate the vSphere Cloud configuration section. Look for a 'Test Connection' or similar button that validates the vSphere server credentials.
    Affected if The vSphere configuration section with a test connection feature is present and accessible to users with configuration privileges.

You are affected if the vSphere Plugin is installed at version 2.16 or any earlier version, allowing unauthenticated CSRF requests through the form validation and test connection features.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 2.16
Interim mitigation

Update Jenkins vSphere Plugin to version newer than 2.16, which should include CSRF protection tokens. Additionally, ensure Jenkins global security settings enforce CSRF protection.

Fix this in Vsphere Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-1000153 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-1000153 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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