dbcve.org
Configuration As CodeApplication · Jenkins

CVE-2018-1000610

HIGH · 8.8 CVSS v3.0 Published 2018-06-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 Configuration as Code Plugin 0.7-alpha and earlier in DataBoundConfigurator.java, Attribute.java, BaseConfigurator.java, ExtensionConfigurator.java that allows attackers with access to Jenkins log files to obtain the passwords configured using Configuration as Code Plugin.

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 Configuration as Code Plugin versions 0.7-alpha and earlier writes configured passwords in plaintext to Jenkins log files. The vulnerability exists in multiple Java classes (DataBoundConfigurator.java, Attribute.java, BaseConfigurator.java, ExtensionConfigurator.java), allowing attackers with access to log files to retrieve sensitive credentials.

MitigationUpgrade Jenkins Configuration as Code Plugin to a version later than 0.7-alpha. Additionally, audit and rotate any credentials that may have been exposed in log files, and restrict access to Jenkins log files as a defense-in-depth measure.

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
Configuration As CodeApplication
Affected:= 0.1= 0.2= 0.3= 0.4= 0.5= 0.6= 0.7

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 Jenkins Configuration as Code Plugin is installed
    In the Jenkins web UI, go to Manage Jenkins > Manage Plugins > Installed tab and look for 'Configuration as Code' in the list, or run: jenkins-cli.jar who-am-i (or check $JENKINS_HOME/plugin directory for the jcasc-plugin folder)
    Affected if The plugin is installed and the version is 0.7-alpha or earlier (versions 0.1 through 0.7-alpha are affected)
  2. Identify the exact plugin version
    Click on the Configuration as Code plugin in the Installed tab to view its version, or examine the manifest file within the plugin .hpi file in $JENKINS_HOME/plugins/
    Affected if Version displayed is 0.7-alpha or any version from 0.1 through 0.6 inclusive
  3. Determine if JCasC configuration contains sensitive credentials
    Locate the Configuration as Code configuration file (typically referenced in Manage Jenkins > Configuration as Code > View Configuration, or check the configured jcasc file path in Jenkins system configuration) and review it for any password, secret, or credential fields
    Affected if The JCasC configuration defines sensitive fields such as passwords, secrets, or credentials that could be logged
  4. Inspect Jenkins log files for plaintext passwords
    Examine Jenkins log files (typically found in $JENKINS_HOME/logs/ or the main jenkins.log file) and search for plaintext sensitive values that appear in configuration sections, especially around lines mentioning 'password', 'secret', or credential-related keywords
    Affected if Any configured passwords, secrets, or credentials from the JCasC configuration appear in plaintext in the logs
  5. Review log patterns around configuration reload events
    When the Configuration as Code plugin loads or reloads configuration (triggered manually or at startup), examine the logs for that period - the vulnerability occurs during the configuration binding process in the DataBoundConfigurator and related classes
    Affected if Log entries during configuration load contain plaintext representations of sensitive field values

A user is affected if the Configuration as Code Plugin version is 0.7-alpha or earlier AND the JCasC configuration contains sensitive credentials that could have been written to logs in plaintext.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Jenkins Configuration as Code Plugin to a version later than 0.7-alpha. Additionally, audit and rotate any credentials that may have been exposed in log files, and restrict access to Jenkins log files as a defense-in-depth measure.

Fix this in Configuration As Code Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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