dbcve.org
Openstack CloudApplication · Jenkins

CVE-2018-1000603

HIGH · 8.8 CVSS v3.0 Published 2018-06-26
Fix available
A fix is available. Upgrade to after 2.35 or later.
See remediation →
94/100
Remediation priority · Urgent
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
A exposure of sensitive information vulnerability exists in Jenkins Openstack Cloud Plugin 2.35 and earlier in BootSource.java, InstancesToRun.java, JCloudsCleanupThread.java, JCloudsCloud.java, JCloudsComputer.java, JCloudsPreCreationThread.java, JCloudsRetentionStrategy.java, JCloudsSlave.java, JCloudsSlaveTemplate.java, LauncherFactory.java, OpenstackCredentials.java, OpenStackMachineStep.java, SlaveOptions.java, SlaveOptionsDescriptor.java that allows attackers with Overall/Read access to Jenkins to connect to an attacker-specified URL using attacker-specified credentials IDs obtained through another method, capturing credentials stored in Jenkins, and to cause Jenkins to submit HTTP requests to attacker-specified URLs.

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

The Jenkins Openstack Cloud Plugin versions 2.35 and earlier allows attackers with Overall/Read access to connect to attacker-specified URLs using attacker-specified credentials IDs, enabling capture of stored Jenkins credentials and SSRF attacks where Jenkins submits HTTP requests to attacker-controlled URLs. The vulnerability exists across multiple Java files handling credential management and cloud operations.

MitigationUpdate Jenkins Openstack Cloud Plugin to a version newer than 2.35 to patch the credential exposure and SSRF vulnerability. If immediate update is not possible, restrict Overall/Read access to trusted users only.

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
Openstack CloudApplication
Affected:<= 2.35

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
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:L/UI:N/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. Verify Openstack Cloud Plugin is installed
    Go to Manage Jenkins > Manage Plugins > Installed tab and search for 'Openstack' in the filter, or check the $JENKINS_HOME/plugins directory for the openstack folder
    Affected if The Openstack Cloud Plugin appears in the installed plugins list
  2. Check installed plugin version
    In Jenkins UI, go to Manage Jenkins > Manage Plugins > Installed tab, find Openstack Cloud Plugin, and note the version column. Alternatively, inspect $JENKINS_HOME/plugins/openstack/META-INF/MANIFEST.MF for the Implementation-Version
    Affected if The version is 2.35 or lower
  3. Verify cloud configuration exists
    Go to Manage Jenkins > Configure System and look for an 'Openstack Cloud' section, or check $JENKINS_HOME/org.jenkinsci.plugins.openstack.cloud.CloudList.xml for cloud configurations
    Affected if At least one Openstack Cloud configuration is defined with an endpoint URL and credentials
  4. Check for Overall/Read access users
    Go to Manage Jenkins > Manage Users and then check People > Matrix-based security in Manage Jenkins > Configure Global Security to see which users or groups have Overall/Read permission
    Affected if Non-administrative users or groups have been granted Overall/Read permission, allowing them to access the vulnerable credential/URL submission endpoints

You are affected if the Openstack Cloud Plugin version is 2.35 or earlier AND non-administrative users have Overall/Read access AND an Openstack Cloud configuration exists in your Jenkins instance.

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.35
Interim mitigation

Update Jenkins Openstack Cloud Plugin to a version newer than 2.35 to patch the credential exposure and SSRF vulnerability. If immediate update is not possible, restrict Overall/Read access to trusted users only.

Fix this in Openstack Cloud Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
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,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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