Dynamic Extended Choice ParameterApplication · Jenkins
CVE-2022-34186
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 Dynamic Extended Choice Parameter Plugin 1.0.1 and earlier does not escape the name and description of Moded 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 confidenceThe Jenkins Dynamic Extended Choice Parameter Plugin versions 1.0.1 and earlier fails to properly escape HTML entities in the name and description fields of Moded Extended Choice parameters when rendered on parameter display views. This allows an attacker with Item/Configure permission to inject malicious JavaScript code that executes in the browsers of other users viewing those parameters.
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
Dynamic Extended Choice ParameterApplication
<= 1.0.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
- 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 the Dynamic Extended Choice Parameter plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed and search for 'Dynamic Extended Choice Parameter' in the list of installed pluginsAffected if The plugin appears in the installed plugins list
-
Confirm the installed versionIn the Installed plugins list, locate the Dynamic Extended Choice Parameter plugin and note the Version column. Compare this version to 1.0.1 or earlierAffected if The installed version is 1.0.1 or lower
-
Identify jobs using Moded Extended Choice parametersReview job configuration files (config.xml) or manually inspect job configurations in the UI for 'Moded Extended Choice' parameter types in the Build Parameters sectionAffected if Any job contains a Moded Extended Choice parameter with custom name or description fields
-
Check for untrusted users with Item/Configure permissionNavigate to Manage Jenkins > Manage Users and review which users have Item/Configure or Job/Configure permissions, particularly on jobs using the affected parameter typeAffected if Users who are not fully trusted have Configure permission on jobs that use Moded Extended Choice parameters
-
Inspect parameter name and description fields for unsanitized contentView the configured Moded Extended Choice parameters in job configuration pages. Look at the Name and Description fields for any content that contains HTML markup, script tags, or special characters that might appear unescaped when renderedAffected if The name or description fields contain raw HTML, JavaScript, or appear to render as markup rather than plain text
A user is affected if the Dynamic Extended Choice Parameter plugin version 1.0.1 or earlier is installed AND Moded Extended Choice parameters are configured with untrusted users having Item/Configure permission.
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 the plugin to a version that properly escapes the name and description fields using appropriate HTML encoding functions. Until patched, limit Configure permission to trusted users only.
Fix this in Dynamic Extended Choice Parameter
Scoped from the published advisory
- Consultation1.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 $1,904.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-34186 — 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-34186 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