Stash Branch ParameterApplication · Jenkins
CVE-2022-34198
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 Stash Branch Parameter Plugin 0.3.0 and earlier does not escape the name and description of Stash Branch parameters on views displaying parameters, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers with Item/Configure permission.
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 confidenceThe Jenkins Stash Branch Parameter Plugin versions 0.3.0 and earlier does not escape the name and description fields of Stash Branch parameters when rendering them in the UI. This allows an attacker with Item/Configure permission to inject malicious JavaScript code into these fields, which executes when other users view the parameters page, resulting in a stored XSS vulnerability.
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
Stash Branch ParameterApplication
<= 0.3.0CVSS 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
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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.
-
Verify Stash Branch Parameter plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab, or use the Jenkins script console: Jenkins.instance.pluginManager.plugins.collect { it.shortName }.contains('stash-branch-parameter')Affected if The plugin is present in the Jenkins instance
-
Check installed plugin versionIn Manage Plugins > Installed, find the Stash Branch Parameter plugin and note the Version column, or use the script console: Jenkins.instance.pluginManager.plugins.find { it.shortName == 'stash-branch-parameter' }.versionAffected if Version is 0.3.0 or earlier
-
Identify jobs using Stash Branch ParameterUse the Jenkins script console to search for jobs with Stash Branch Parameter definitions: Jenkins.instance.allItems.collect { job -> [name: job.fullName, params: job.properties.find { it.class.simpleName == 'ParametersDefinitionProperty' }?.parameterDefinitions.findAll { it.class.name.contains('StashBranchParameter') }] }.findAll { it.params }Affected if Any jobs are found that use Stash Branch Parameter definitions
-
Inspect parameter name and description fieldsReview each Stash Branch Parameter definition found and examine the 'name' and 'description' fields for unexpected characters such as <script>, javascript:, onload, or other HTML/JavaScript codeAffected if The name or description fields contain unescaped HTML or JavaScript code that could execute in a user's browser
The environment is affected if the Stash Branch Parameter plugin version 0.3.0 or earlier is installed AND at least one job has a Stash Branch Parameter configured with injectable content in the name or description fields.
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.
From vendor dataUpdate to a patched version of the Stash Branch Parameter Plugin when available. In the interim, restrict Item/Configure permission to trusted users only and review existing configurations for malicious parameter definitions.
Fix this in Stash Branch Parameter
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-34198 — 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-34198 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