Jenkins Parameterized Trigger Plugin 2.43 and earlier captures environment variables passed to builds triggered using Jenkins Parameterized Trigger Plugin, including password parameter values, in their build.xml files. These values are stored unencrypted and can be viewed by users with access to the Jenkins controller file system.

Existing build.xml files are not automatically updated to remove captured environment variables. They need to be manually cleaned up. To help with this, the plugin will report environment variables stored in build.xml as unloadable data in the Old Data Monitor, that allows discarding this data. Build records are only loaded from disk when needed however, so some builds stored in Jenkins may not immediately appear there.

References

• https://nvd.nist.gov/vuln/detail/CVE-2022-27195
• https://www.jenkins.io/security/advisory/2022-03-15/#SECURITY-2185
• http://www.openwall.com/lists/oss-security/2022/03/15/2
• jenkinsci/parameterized-trigger-plugin@6b7cd22
• jenkinsci/parameterized-trigger-plugin@b5ec2b4