CVE-2019-10367: Configuration as code Insertion Of Sensitive Information Into Vulnerability

MODERATE
Advisory Identifier: GHSA-7c3v-vc3x-x789
Share
CVSS 5.5
CWE-532
Published
Advisory Summary

CVE-2019-10367 is a MODERATE (CVSS 5.5) insertion of sensitive information into vulnerability (CWE-532: Insertion of Sensitive Information into Log File) affecting Configuration as code libraries in the Maven ecosystem. The issue involves insertion of sensitive information into log file in jenkins configuration as code plugin. Remediation is available by upgrading affected packages to version 1.27.

CVE-2019-10367 at a Glance

CVE Identifier CVE-2019-10367
GHSA Identifier GHSA-7c3v-vc3x-x789
Severity MODERATE
CVSS v3.1 Base Score 5.5
CWE Classification CWE-532: Insertion of Sensitive Information into Log File
Affected Product Configuration as code
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 5.5

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

Attack Vector Local (AV:L)
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-2019-10367

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: 1.27 
<dependency>
    <groupId>io.jenkins</groupId>
    <artifactId>configuration-as-code</artifactId>
    <version>1.27</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-2019-10367, 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 1.27), 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-532: Insertion of Sensitive Information into Log File, where the product writes sensitive information to a log file. 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

Configuration as Code Plugin logs the changes it applies to the Jenkins system log. Secrets such as passwords should be masked (i.e. replaced with asterisks) in that log to prevent accidental disclosure. Configuration as Code Plugin inspects the type and looks for a field, getter, or constructor argument corresponding to the property, making the secret detection much more robust for the purpose of log message masking. This was implemented in the [fix for SECURITY-1279 in the 2019-07-31 security advisory](https://www.jenkins.io/security/advisory/2019-07-31/#SECURITY-1279). That fix was incomplete and did not cover a log message written to the logger `io.jenkins.plugins.casc.impl.configurators.DataBoundConfigurator`. Configuration as Code Plugin now uses the same secret detection for these log messages. As a workaround, administrators can configure the logging level of the logger `io.jenkins.plugins.casc.impl.configurators.DataBoundConfigurator` to a level that does not include these messages. Configuration as Code Plugin 1.25 and earlier logs these messages at the `INFO` level, Configuration as Code Plugin 1.26 logs them at `FINE`. See the logging documentation for details.

CVE-2019-10367 Affected Configuration as code Versions

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

References

NVD — CVE-2019-10367 NVD
https://nvd.nist.gov/vuln/detail/CVE-2019-10367
Security Fix Commit FIX COMMIT
https://github.com/jenkinsci/configuration-as-code-plugin/commit/322ef83f3200ce6076129c014209ef938e556774
Configuration as code Security Information SECURITY
https://jenkins.io/security/advisory/2019-08-07/#SECURITY-1497
Configuration as code Security Information SECURITY
https://www.jenkins.io/security/advisory/2019-07-31/#SECURITY-1279
Configuration as code Security Information SECURITY
http://www.openwall.com/lists/oss-security/2019/08/07/1

Frequently Asked Questions

What is CVE-2019-10367?
CVE-2019-10367 is a security vulnerability in Configuration as code involving Insertion of Sensitive Information into Log File in Jenkins Configuration as Code Plugin under CWE-532: Insertion of Sensitive Information into Log File.
Which Configuration as code versions are affected?
Affected versions include releases prior to 1.27 across affected packages: io.jenkins:configuration-as-code.
What version fixes CVE-2019-10367?
Upgrading to 1.27 (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 1.27. Upgrade your dependency to 1.27 or later.
What is the CVSS score of CVE-2019-10367?
CVE-2019-10367 has a CVSS v3.1 base score of 5.5 (MODERATE) with vector string CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N.
What CWE is associated with CVE-2019-10367?
CVE-2019-10367 is classified under CWE-532: Insertion of Sensitive Information into Log File (The product writes sensitive information to a log file.).
How can I check Maven dependencies for CVE-2019-10367?
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-7c3v-vc3x-x789",
  "modified" : "2023-10-26T16:24:01Z",
  "published" : "2022-05-24T16:52:44Z",
  "aliases" : [ "CVE-2019-10367" ],
  "summary" : "Insertion of Sensitive Information into Log File in Jenkins Configuration as Code Plugin",
  "details" : "Configuration as Code Plugin logs the changes it applies to the Jenkins system log. Secrets such as passwords should be masked (i.e. replaced with asterisks) in that log to prevent accidental disclosure. Configuration as Code Plugin inspects the type and looks for a field, getter, or constructor argument corresponding to the property, making the secret detection much more robust for the purpose of log message masking. This was implemented in the [fix for SECURITY-1279 in the 2019-07-31 security advisory](https://www.jenkins.io/security/advisory/2019-07-31/#SECURITY-1279).\n\nThat fix was incomplete and did not cover a log message written to the logger `io.jenkins.plugins.casc.impl.configurators.DataBoundConfigurator`.\n\nConfiguration as Code Plugin now uses the same secret detection for these log messages.\n\nAs a workaround, administrators can configure the logging level of the logger `io.jenkins.plugins.casc.impl.configurators.DataBoundConfigurator` to a level that does not include these messages. Configuration as Code Plugin 1.25 and earlier logs these messages at the `INFO` level, Configuration as Code Plugin 1.26 logs them at `FINE`. See the logging documentation for details.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/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" : "1.27"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 1.26"
    }
  } ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2019-10367"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/jenkinsci/configuration-as-code-plugin/commit/322ef83f3200ce6076129c014209ef938e556774"
  }, {
    "type" : "WEB",
    "url" : "https://jenkins.io/security/advisory/2019-08-07/#SECURITY-1497"
  }, {
    "type" : "WEB",
    "url" : "https://www.jenkins.io/security/advisory/2019-07-31/#SECURITY-1279"
  }, {
    "type" : "WEB",
    "url" : "http://www.openwall.com/lists/oss-security/2019/08/07/1"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-532" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2022-06-28T22:36:48Z",
    "nvd_published_at" : "2019-08-07T15:15:00Z"
  }
}