dbcve.org
VsphereApplication · Jenkins

CVE-2018-1000152

MEDIUM · 6.3 CVSS v3.0 Published 2018-04-05
Fix available
A fix is available. Upgrade to after 2.16 or later.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable Zero-click

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
An improper authorization 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

Improper authorization vulnerability in Jenkins vSphere Plugin 2.16 and older allows unauthenticated or unauthorized attackers to perform form validation actions, including sending repeated requests to the configured vSphere server (potential DoS) and abusing the 'test connection' feature to exfiltrate Jenkins credentials to attacker-controlled servers.

MitigationUpgrade vSphere Plugin to version 2.17 or later which contains proper authorization checks. If upgrade is not immediately possible, restrict access to Jenkins and vSphere credentials until patching can be completed.

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

CVSS:3.0/AV:N/AC:L/PR:L/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 checks

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

  1. Identify if vSphere Plugin is installed
    In Jenkins, go to Manage Jenkins > Manage Plugins > Installed tab and search for 'vSphere' or 'vsphere' in the plugin list. Alternatively, check the plugin directory (typically $JENKINS_HOME/plugins/) for the vsphere-plugin folder.
    Affected if The vSphere Plugin appears in the installed plugins list
  2. Determine the installed vSphere Plugin version
    In Jenkins plugin manager, click on the vSphere Plugin entry to view its version. The version number is displayed in the plugin details panel.
    Affected if The installed version is 2.16 or older (e.g., 2.15, 2.14, etc.)
  3. Check if the plugin has active vSphere configurations
    Navigate to Jenkins > Manage Jenkins > Configure (or look for vSphere-related configuration pages). Verify if any vSphere servers are configured with credentials.
    Affected if vSphere servers are configured and the plugin is actively used with stored credentials
  4. Verify Jenkins access control settings
    Check Jenkins security configuration under Manage Jenkins > Configure Global Security. Determine whether anonymous users have any access or whether the 'Overall/Read' permission is granted to anonymous users.
    Affected if Anonymous access is permitted or authentication is not enforced on form validation endpoints

You are affected if the vSphere Plugin version is 2.16 or older AND the plugin is configured with vSphere credentials, especially if Jenkins allows anonymous or unauthenticated access.

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

Upgrade vSphere Plugin to version 2.17 or later which contains proper authorization checks. If upgrade is not immediately possible, restrict access to Jenkins and vSphere credentials until patching can be completed.

Fix this in Vsphere Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-1000152 — 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-1000152 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