https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Mon, 12 Oct 2026 22:43:02 +0000 https://cve.radiocsirt.org/vuln/cnvd-2019-28230 cnvd-2019-28230 https://cve.radiocsirt.org/vuln/cnvd-2019-28230 https://cve.radiocsirt.org/vuln/euvd-2026-53572 EUVD-2026-53572 https://cve.radiocsirt.org/vuln/euvd-2026-53572 https://cve.radiocsirt.org/vuln/fkie_cve-2019-10367 <p>Due to an incomplete fix of CVE-2019-10343, Jenkins Configuration as Code Plugin 1.26 and earlier did not properly apply masking to some values expected to be hidden when logging the configuration being applied.</p> <p>Due to an incomplete fix of CVE-2019-10343, Jenkins Configuration as Code Plugin 1.26 and earlier did not properly apply masking to some values expected to be hidden when logging the configuration being applied.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2019-10367 https://cve.radiocsirt.org/vuln/ghsa-7c3v-vc3x-x789 <p><strong>Affected:</strong> Maven: io.jenkins:configuration-as-code</p> <p>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).</p> <p>That fix was incomplete and did not cover a log message written to the logger `io.jenkins.plugins.casc.impl.configurators.DataBoundConfigurator`.</p> <p>Configuration as Code Plugin now uses the same secret detection for these log messages.</p> <p>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.</p> <p><strong>Affected:</strong> Maven: io.jenkins:configuration-as-code</p> <p>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).</p> <p>That fix was incomplete and did not cover a log message written to the logger `io.jenkins.plugins.casc.impl.configurators.DataBoundConfigurator`.</p> <p>Configuration as Code Plugin now uses the same secret detection for these log messages.</p> <p>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.</p> https://cve.radiocsirt.org/vuln/ghsa-7c3v-vc3x-x789 https://cve.radiocsirt.org/vuln/gsd-2019-10367 gsd-2019-10367 https://cve.radiocsirt.org/vuln/gsd-2019-10367