dbcve.org
Rest List ParameterApplication · Jenkins

CVE-2022-34196

MEDIUM · 5.4 CVSS v3.1 Published 2022-06-23
Fix available
A fix is available. Upgrade to after 1.5.2 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
Jenkins REST List Parameter Plugin 1.5.2 and earlier does not escape the name and description of REST list 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 confidence

The Jenkins REST List Parameter Plugin versions 1.5.2 and earlier fail to properly escape HTML characters in the name and description fields of REST list parameters when rendered in parameter display views. This allows attackers with Item/Configure permission to inject malicious JavaScript code that executes in the browsers of other users viewing those parameters, representing a stored cross-site scripting vulnerability.

MitigationUpgrade to a patched version of the REST List Parameter Plugin that properly escapes parameter names and descriptions, or implement HTML encoding on all user-controlled parameter fields before rendering them in views.

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
Rest List ParameterApplication
Affected:<= 1.5.2

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify REST List Parameter plugin is installed
    Locate the plugin in the Jenkins plugins directory (typically $JENKINS_HOME/plugins/rest-list-parameter/) or query via Jenkins script console: Jenkins.instance.pluginManager.getPlugin('rest-list-parameter')
    Affected if Plugin is present in the Jenkins instance
  2. Check installed plugin version
    Inspect the plugin's manifest file (META-INF/MANIFEST.MF) inside the plugin directory, or retrieve via Jenkins API: Jenkins.instance.pluginManager.getPlugin('rest-list-parameter').getVersion()
    Affected if Version is 1.5.2 or lower
  3. Identify jobs using REST list parameters
    Search job configurations for '<hudson.plugins.restlistparameter.RestListParameterDefinition>' XML elements, or use Jenkins script: Jenkins.instance.allItems.collect{job -> job.actions.findAll{it.class.simpleName == 'ParametersAction'}}.flatten()
    Affected if Any jobs are configured with REST list parameters
  4. Inspect parameter name and description fields
    Examine the configuration XML for each REST list parameter found, looking at the <name> and <description> child elements
    Affected if Parameters contain unsanitized HTML or JavaScript in name or description fields that render unescaped in the UI

User is affected if the REST List Parameter Plugin version 1.5.2 or lower is installed AND any job is configured with REST list parameters that contain HTML/JavaScript content in name or description fields.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to a release after 1.5.2
Interim mitigation

Upgrade to a patched version of the REST List Parameter Plugin that properly escapes parameter names and descriptions, or implement HTML encoding on all user-controlled parameter fields before rendering them in views.

Recommended fix High confidence

1.5.3

  1. Navigate to 'Manage Jenkins' > 'Manage Plugins'
  2. Go to the 'Installed' tab
  3. Locate the 'REST List Parameter' plugin
  4. If the plugin shows version 1.5.2 or earlier, click 'Update now' to upgrade to version 1.5.3 or later
  5. Restart Jenkins if required after the update

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Rest List Parameter Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-34196 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-34196 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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