Password disclosure via persisted build environment variables
Published Mar 15, 2022 · Updated Aug 3, 2024
Sensitive-data exposure in Jenkins Parameterized Trigger Plugin 2.43 and earlier allows local users to read build parameters from disk. CapturedEnvironmentAction retains EnvVars as a serializable field, causing Jenkins to persist the build environment, including password parameters, in build.xml. Access requires the Jenkins controller filesystem, and the exposed data is limited to environment values captured for affected triggered builds.
Summary
What happened
Sensitive-data exposure in Jenkins Parameterized Trigger Plugin 2.43 and earlier allows local users to read build parameters from disk. CapturedEnvironmentAction retains EnvVars as a serializable field, causing Jenkins to persist the build environment, including password parameters, in build.xml. Access requires the Jenkins controller filesystem, and the exposed data is limited to environment values captured for affected triggered builds.
The record
- CVE
- CVE-2022-27195
- Published
- Mar 15, 2022
- Updated
- Aug 3, 2024
- Vendor
- Jenkins Project
- Product
- Parameterized Trigger Plugin
- Classifications
- CWE-532, T1552.001
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 15, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified <=2.43
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo