GitHub Advisoryadvisory · Maven

GHSA-5mpf-hw8f-86w9 Sensitive parameter values captured in build metadata files by Jenkins Parameterized Trigger Plugin

LOW Published 2022-03-16 Modified 2022-11-30 Official page ↗
Aliases
CVE-2022-27195
Ecosystem
Maven
Packages
org.jenkins-ci.plugins:parameterized-trigger
Severity
Low
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
Weaknesses
CWE-532
Reviewed
2022-11-30

Affected packages

• Maven org.jenkins-ci.plugins:parameterized-trigger: < 2.43.1 → fixed in 2.43.1

Description

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.

Related

Alias · CVE (1)

  • CVE-2022-27195 Jenkins Parameterized Trigger Plugin 2.43 and earlier captures environment variables passed to builds triggered using Jenkins Parameterized… vulnerability

Weakness · CWE (1)

  • CWE-532 Insertion of Sensitive Information into Log File weakness

References