Vulnerabilities in pkg:maven/io.jenkins/configuration-as-code

PACKAGE
Advisory Identifier: GHSA-vwq9-cmqr-3c8c
Advisory Summary

CVE-2019-10343 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.25.

9 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:maven/io.jenkins/configuration-as-code

9 Known Advisory Record(s)

Vulnerability advisories affecting package pkg:maven/io.jenkins/configuration-as-code. Select an advisory below to view technical details or fixes.

Advisory ID CVE / NVD Severity Summary
GHSA-vwq9-cmqr-3c8c CVE-2019-10343 MODERATE Insertion of Sensitive Information into Log File in Jenkins Configuration as Code Plugin
GHSA-7c3v-vc3x-x789 CVE-2019-10367 MODERATE Insertion of Sensitive Information into Log File in Jenkins Configuration as Code Plugin
GHSA-fpj7-9xm6-8hgr CVE-2022-23106 LOW Observable Discrepancy and Observable Timing Discrepancy in Jenkins Configuration as Code Plugin
GHSA-393r-r9mq-g9jv CVE-2018-1000609 MODERATE Jenkins Configuration as Code Plugin vulnerable to Exposure of Sensitive Information
GHSA-8486-h39x-cx2f CVE-2018-1000610 HIGH Jenkins Configuration as Code Plugin has Insufficiently Protected Credentials
GHSA-mqr8-3v8j-46wv CVE-2019-10344 MODERATE Missing Authorization in Jenkins Configuration as Code Plugin
GHSA-ggmx-pq89-7mcr CVE-2019-10345 MODERATE Plaintext Storage of a Password in Jenkins Configuration as Code Plugin
GHSA-5r6p-p9r6-r326 CVE-2019-10362 MODERATE Improper Encoding or Escaping of Output in Jenkins Configuration as Code Plugin
GHSA-r69h-6c4g-63xf CVE-2019-10363 MODERATE Cleartext Transmission of Sensitive Information in Jenkins Configuration as Code Plugin

CVE-2019-10343 at a Glance

CVE Identifier CVE-2019-10343
GHSA Identifier GHSA-vwq9-cmqr-3c8c
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.0/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-10343

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.25
<dependency>
    <groupId>io.jenkins</groupId>
    <artifactId>configuration-as-code</artifactId>
    <version>1.25</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-10343, 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.25), 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. Between Configuration as Code Plugin 0.8-alpha and 1.0, log messages contained values if the values were specified using properties in the YAML file (SECURITY-929). Since Configuration as Code Plugin 1.1, log messages in Configuration as Code Plugin instead mask values of type `Secret`, which is used in Jenkins to store the values encrypted on disk. This did not work in many instances, as plugins could use the `Secret` type to store credentials encrypted on disk while not having the Secret type appear in their Java API. Configuration as Code Plugin now 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. As a workaround, administrators can configure the logging level of the logger `io.jenkins.plugins.casc.Attribute` to a level that does not include `INFO` messages. See the logging documentation for details.

CVE-2019-10343 Affected Configuration as code Versions

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

References

Frequently Asked Questions

What is CVE-2019-10343?
CVE-2019-10343 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.25 across affected packages: io.jenkins:configuration-as-code.
What version fixes CVE-2019-10343?
Upgrading to 1.25 (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.25. Upgrade your dependency to 1.25 or later.
What is the CVSS score of CVE-2019-10343?
CVE-2019-10343 has a CVSS v3.1 base score of 5.5 (MODERATE) with vector string CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N.
What CWE is associated with CVE-2019-10343?
CVE-2019-10343 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-10343?
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
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-vwq9-cmqr-3c8c",
  "modified" : "2023-10-26T16:44:50Z",
  "published" : "2022-05-24T16:51:50Z",
  "aliases" : [ "CVE-2019-10343" ],
  "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.\n\nBetween Configuration as Code Plugin 0.8-alpha and 1.0, log messages contained values if the values were specified using properties in the YAML file (SECURITY-929).\n\nSince Configuration as Code Plugin 1.1, log messages in Configuration as Code Plugin instead mask values of type `Secret`, which is used in Jenkins to store the values encrypted on disk. This did not work in many instances, as plugins could use the `Secret` type to store credentials encrypted on disk while not having the Secret type appear in their Java API.\n\nConfiguration as Code Plugin now 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. As a workaround, administrators can configure the logging level of the logger `io.jenkins.plugins.casc.Attribute` to a level that does not include `INFO` messages. See the logging documentation for details.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.0/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.25"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 1.24"
    }
  } ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2019-10343"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/jenkinsci/configuration-as-code-plugin/commit/73afe3cb10a723cb06e29c2e5499206aadae3a0d"
  }, {
    "type" : "WEB",
    "url" : "https://jenkins.io/security/advisory/2019-07-31/#SECURITY-1279"
  }, {
    "type" : "WEB",
    "url" : "http://www.openwall.com/lists/oss-security/2019/07/31/1"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-532" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2022-06-28T23:08:40Z",
    "nvd_published_at" : "2019-07-31T13:15:00Z"
  }
}