dbcve.org
KubernetesApplication · Jenkins

CVE-2018-1000187

MEDIUM · 6.5 CVSS v3.0 Published 2018-06-05
Fix available
A fix is available. Upgrade to after 1.7.0 or later.
See remediation →
71/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
A exposure of sensitive information vulnerability exists in Jenkins Kubernetes Plugin 1.7.0 and older in ContainerExecDecorator.java that results in sensitive variables such as passwords being written to logs.

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 Kubernetes Plugin versions 1.7.0 and older contains a vulnerability in ContainerExecDecorator.java where sensitive variables such as passwords are written to the Jenkins logs, exposing them to unauthorized users with log access.

MitigationUpgrade the Jenkins Kubernetes Plugin to a version newer than 1.7.0, and audit existing logs for any exposed credentials.

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
KubernetesApplication
Affected:<= 1.7.0

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
None
Availability
None

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

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. Check installed Jenkins Kubernetes Plugin version
    Navigate to Manage Jenkins > Manage Plugins > Installed tab, or use the Jenkins CLI: java -jar jenkins-cli.jar -s http://[jenkins-url] list-plugins | grep kubernetes
    Affected if The plugin version is 1.7.0 or older (1.7.0, 1.6.0, etc.)
  2. Confirm Kubernetes plugin is actively used
    Check Jenkins job configurations for jobs using the Kubernetes cloud/label, or inspect the Jenkins configuration (Manage Jenkins > Configure System > Cloud) for Kubernetes cloud configurations
    Affected if The Kubernetes plugin is configured and actively managing build agents or pods
  3. Examine Jenkins logs for exposed credentials
    Review Jenkins logs (Manage Jenkins > System Log) or the job build logs for patterns like 'password', 'secret', 'token', or similar sensitive terms that may have been inadvertently logged during container execution
    Affected if Log entries containing cleartext passwords, secrets, or tokens from Kubernetes pod/container operations are present

A user is affected if the Jenkins Kubernetes Plugin version is 1.7.0 or older, the plugin is in use, and sensitive credentials may have been written to accessible logs.

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 1.7.0
Interim mitigation

Upgrade the Jenkins Kubernetes Plugin to a version newer than 1.7.0, and audit existing logs for any exposed credentials.

Fix this in Kubernetes Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,590
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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