Jenkins Parameterized Trigger Plugin
Approved changes feed: RSS · Atom
cpe:2.3:a:jenkins_project:jenkins_parameterized_trigger_plugin:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Jenkins Project (860cd631-1316-551d-89a3-5aa9a0d4f462) |
|---|---|
| Product | Jenkins Parameterized Trigger Plugin (7789f97d-2248-5802-aa3b-a9fbe1f3ec7d) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2022-27195 |
vulnerable | 2026-06-08 05:41:54.983668 |
Details available
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.
Published: 2022-03-15T16:45:37.000Z
Updated: 2024-08-03T05:25:31.103Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.