https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Mon, 12 Oct 2026 21:58:35 +0000 https://cve.radiocsirt.org/vuln/cnvd-2019-26377 cnvd-2019-26377 https://cve.radiocsirt.org/vuln/cnvd-2019-26377 https://cve.radiocsirt.org/vuln/euvd-2026-53593 EUVD-2026-53593 https://cve.radiocsirt.org/vuln/euvd-2026-53593 https://cve.radiocsirt.org/vuln/fkie_cve-2019-10343 <p>Jenkins Configuration as Code Plugin 1.24 and earlier did not properly apply masking to values expected to be hidden when logging the configuration being applied.</p> <p>Jenkins Configuration as Code Plugin 1.24 and earlier did not properly apply masking to values expected to be hidden when logging the configuration being applied.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2019-10343 https://cve.radiocsirt.org/vuln/ghsa-vwq9-cmqr-3c8c <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.</p> <p>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).</p> <p>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.</p> <p>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.</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.</p> <p>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).</p> <p>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.</p> <p>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.</p> https://cve.radiocsirt.org/vuln/ghsa-vwq9-cmqr-3c8c https://cve.radiocsirt.org/vuln/gsd-2019-10343 gsd-2019-10343 https://cve.radiocsirt.org/vuln/gsd-2019-10343