dbcve.org
Extended Choice ParameterApplication · Jenkins

CVE-2022-29038

MEDIUM · 5.4 CVSS v3.1 Published 2022-04-12
Fix available
A fix is available. Upgrade to after 346.vd87693c5a_86c 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 Extended Choice Parameter Plugin 346.vd87693c5a_86c and earlier does not escape the name and description of Extended Choice 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 Extended Choice Parameter Plugin fails to properly escape HTML in the name and description fields of Extended Choice parameters when rendering them on parameter display views. This allows an attacker with Item/Configure permission to inject malicious JavaScript code that gets stored and executed in the browsers of other users who view the affected parameter pages.

MitigationUpdate the Extended Choice Parameter Plugin to version 346.vd87693c5a_86c or later, which includes proper HTML escaping for parameter names and descriptions. Alternatively, restrict Item/Configure permission to trusted users only until the update can be applied.

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
Extended Choice ParameterApplication
Affected:<= 346.vd87693c5a_86c

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. Check if Extended Choice Parameter Plugin is installed
    Go to Manage Jenkins > Manage Plugins > Installed and search for 'Extended Choice Parameter', or run: jenkins-cli.jar who-am-i or check $JENKINS_HOME/plugins for extended-choice-parameter*
    Affected if Plugin is not installed - not affected. If installed, check version against <= 346.vd87693c5a_86c
  2. Identify jobs using Extended Choice parameters
    Navigate to each job's configuration page and look for parameter definitions, or search job config.xml files for '<hudson.plugins.extendedchoiceparameter.ExtendedChoiceParameterDefinition>'
    Affected if No jobs use Extended Choice parameters - not affected (vulnerability only applies to configured parameters)
  3. Inspect parameter names and descriptions for injected code
    In job configuration, examine every Extended Choice parameter's 'Name' and 'Description' fields. Look for HTML tags, <script> elements, event handlers (onclick, onerror, etc.), or javascript: URLs
    Affected if Any Extended Choice parameter name or description contains raw HTML, script tags, or JavaScript code - potentially affected and exploited
  4. Verify View permission exposes parameters to victims
    Check if jobs with Extended Choice parameters are visible to users without Item/Configure permission. View the parameter build page as a non-privileged user to confirm rendering
    Affected if Untrusted users can view parameter pages where injected scripts would execute in their browsers

You are affected if the Extended Choice Parameter Plugin version is <= 346.vd87693c5a_86c AND you have jobs with Extended Choice parameters whose names or descriptions contain unescaped HTML or script content that could execute in other users' browsers.

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 346.vd87693c5a_86c
Interim mitigation

Update the Extended Choice Parameter Plugin to version 346.vd87693c5a_86c or later, which includes proper HTML escaping for parameter names and descriptions. Alternatively, restrict Item/Configure permission to trusted users only until the update can be applied.

Recommended fix Moderate confidence

Extended Choice Parameter plugin version > 346.vd87693c5a_86c (upgrade to latest stable version)

  1. Navigate to Jenkins dashboard
  2. Go to Manage Jenkins > Manage Plugins
  3. Select the 'Updates' tab
  4. Locate 'Extended Choice Parameter' plugin in the list
  5. If an update is available, select the plugin and click 'Download now and install after restart'
  6. Wait for the plugin to update to a secure version
  7. Restart Jenkins to complete the installation
  8. Alternatively, manually download the updated .hpi file from the Jenkins plugin repository and install via 'Advanced' > 'Upload Plugin'

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

Fix this in Extended Choice Parameter Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-29038 — 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-29038 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