CVE-2019-10367 – io.jenkins:configuration-as-code

Package

Manager: maven
Name: io.jenkins:configuration-as-code
Vulnerable Version: >=0 <1.27

Severity

Level: Medium

CVSS v3.1: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

CVSS v4.0: CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

EPSS: 0.00022 pctl0.04106

Details

Insertion of Sensitive Information into Log File in Jenkins Configuration as Code Plugin 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.

Metadata

Created: 2022-05-24T16:52:44Z
Modified: 2023-10-26T16:24:01Z
Source: https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2022/05/GHSA-7c3v-vc3x-x789/GHSA-7c3v-vc3x-x789.json
CWE IDs: ["CWE-532"]
Alternative ID: GHSA-7c3v-vc3x-x789
Finding: F009
Auto approve: 1