CVE-2018-1000609: Configuration as code Jenkins Configuration As Code Plugin Vulnerability

MODERATE
Advisory Identifier: GHSA-393r-r9mq-g9jv
Share
CVSS 6.5
CWE-200
Published
Advisory Summary

CVE-2018-1000609 is a MODERATE (CVSS 6.5) jenkins configuration as code plugin vulnerability (CWE-200: Exposure of Sensitive Information to an Unauthorized Actor) affecting Configuration as code libraries in the Maven ecosystem. The issue involves jenkins configuration as code plugin vulnerable to exposure of sensitive information. Remediation is available by upgrading affected packages to version 0.8-alpha.

CVE-2018-1000609 at a Glance

CVE Identifier CVE-2018-1000609
GHSA Identifier GHSA-393r-r9mq-g9jv
Severity MODERATE
CVSS v3.1 Base Score 6.5
CWE Classification CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
Affected Product Configuration as code
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 6.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity None (I:N)
Availability None (A:N)

How to Fix CVE-2018-1000609

To remediate this vulnerability, upgrade all affected Configuration as code dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

io.jenkins:configuration-as-code fixed: 0.8-alpha 
<dependency>
    <groupId>io.jenkins</groupId>
    <artifactId>configuration-as-code</artifactId>
    <version>0.8-alpha</version>
</dependency>
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

mvn dependency:tree -Dincludes=io.jenkins

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2018-1000609, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree -Dincludes=io.jenkins

Analyze the terminal output to locate any version of Configuration as code in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.8-alpha), your application is affected.

Note: The mvn dependency:tree -Dincludes=io.jenkins command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-200: Exposure of Sensitive Information to an Unauthorized Actor, where the product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. In Configuration as code, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

A exposure of sensitive information vulnerability exists in Jenkins Configuration as Code Plugin 0.7-alpha and earlier in ConfigurationAsCode.java that allows attackers with Overall/Read access to obtain the YAML export of the Jenkins configuration. Version 0.8-alpha contains a fix for this issue.

CVE-2018-1000609 Affected Configuration as code Versions

1 component(s)
Fixed Versions:
0.8-alpha
Product / Package Ecosystem Affected Versions Fixed Version
io.jenkins:configuration-as-code
maven/io.jenkins/configuration-as-code
Maven
< 0.8-alpha
0.8-alpha

References

NVD — CVE-2018-1000609 NVD
https://nvd.nist.gov/vuln/detail/CVE-2018-1000609
Configuration as code Security Information SECURITY
https://jenkins.io/security/advisory/2018-06-25/#SECURITY-927

Frequently Asked Questions

What is CVE-2018-1000609?
CVE-2018-1000609 is a security vulnerability in Configuration as code involving Jenkins Configuration as Code Plugin vulnerable to Exposure of Sensitive Information under CWE-200: Exposure of Sensitive Information to an Unauthorized Actor.
Which Configuration as code versions are affected?
Affected versions include releases prior to 0.8-alpha across affected packages: io.jenkins:configuration-as-code.
What version fixes CVE-2018-1000609?
Upgrading to 0.8-alpha (or the latest patched release for your respective branch) resolves the vulnerability.
Is configuration-as-code affected?
Yes, io.jenkins:configuration-as-code is affected in releases prior to 0.8-alpha. Upgrade your dependency to 0.8-alpha or later.
What is the CVSS score of CVE-2018-1000609?
CVE-2018-1000609 has a CVSS v3.1 base score of 6.5 (MODERATE) with vector string CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N.
What CWE is associated with CVE-2018-1000609?
CVE-2018-1000609 is classified under CWE-200: Exposure of Sensitive Information to an Unauthorized Actor (The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.).
How can I check Maven dependencies for CVE-2018-1000609?
Run the dependency tree command: 'mvn dependency:tree -Dincludes=io.jenkins'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-393r-r9mq-g9jv",
  "modified" : "2022-11-08T23:06:52Z",
  "published" : "2022-05-14T03:05:26Z",
  "aliases" : [ "CVE-2018-1000609" ],
  "summary" : "Jenkins Configuration as Code Plugin vulnerable to Exposure of Sensitive Information",
  "details" : "A exposure of sensitive information vulnerability exists in Jenkins Configuration as Code Plugin 0.7-alpha and earlier in ConfigurationAsCode.java that allows attackers with Overall/Read access to obtain the YAML export of the Jenkins configuration. Version 0.8-alpha contains a fix for this issue.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Maven",
      "name" : "io.jenkins:configuration-as-code"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.8-alpha"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2018-1000609"
  }, {
    "type" : "WEB",
    "url" : "https://jenkins.io/security/advisory/2018-06-25/#SECURITY-927"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-200" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2022-11-08T23:06:52Z",
    "nvd_published_at" : "2018-06-26T17:29:00Z"
  }
}