Parameterized TriggerApplication · Jenkins
CVE-2022-27195
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedJenkins 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceJenkins Parameterized Trigger Plugin versions 2.43 and earlier stores environment variables, including password parameter values, in plain text within build.xml files. Users with filesystem access to the Jenkins controller can read these unencrypted sensitive credentials.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Parameterized TriggerApplication
< 2.43.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Parameterized Trigger Plugin versionNavigate to Manage Jenkins > Manage Plugins > Installed tab, or inspect the plugin's .jpi file metadata in $JENKINS_HOME/plugins/parameterized-trigger-plugin/Affected if Installed version is 2.43 or earlier (less than 2.43.1)
-
Confirm parameterized builds were executedLook for job configurations that use the 'Parameterized Trigger Plugin' build step or parameter triggers, typically in $JENKINS_HOME/jobs/<jobname>/config.xmlAffected if Jobs have used the plugin to trigger builds with parameters
-
Locate build.xml files with stored environment variablesSearch in $JENKINS_HOME/jobs/<jobname>/builds/<buildnumber>/build.xml for XML elements containing <env> or <parameterValues>Affected if Build history contains build.xml files from parameterized builds
-
Inspect build.xml for plain text sensitive valuesOpen a build.xml file from a parameterized build and search for plaintext passwords, API keys, or other credentials within <name> and <value> tags under parameter or environment variable sectionsAffected if Credentials appear in plain text rather than encrypted strings (look for actual password/API key strings, not hashed or masked values)
Environment is affected if the Parameterized Trigger Plugin version is below 2.43.1 AND build.xml files from parameterized builds exist containing plaintext sensitive parameter values.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2.43.1
Upgrade the Jenkins Parameterized Trigger Plugin to version 2.44 or later, which encrypts or prevents storage of sensitive parameters in build.xml files.
Parameterized Trigger Plugin version 2.43.1
- 1. From the Jenkins dashboard, navigate to 'Manage Jenkins'
- 2. Click on 'Manage Plugins'
- 3. Select the 'Updates' tab
- 4. Locate 'Parameterized Trigger Plugin' in the list of available updates
- 5. Check the checkbox next to the plugin
- 6. Click 'Download now and install after restart'
- 7. Wait for the download to complete
- 8. Check the 'Restart Jenkins' checkbox to restart Jenkins and complete the installation
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Parameterized Trigger
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-27195 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-27195 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data