dbcve.org
Crx Content Package DeployerApplication · Jenkins

CVE-2022-34184

MEDIUM · 5.4 CVSS v3.1 Published 2022-06-23
Fix available
A fix is available. Upgrade to after 1.9 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 CRX Content Package Deployer Plugin 1.9 and earlier does not escape the name and description of CRX Content Package 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 CRX Content Package Deployer Plugin versions 1.9 and earlier fails to properly escape the name and description fields of CRX Content Package Choice parameters when displaying them on parameter view pages. This creates a stored cross-site scripting (XSS) vulnerability that can be exploited by users with Item/Configure permissions.

MitigationUpgrade to Jenkins CRX Content Package Deployer Plugin version 1.10 or later which includes proper escaping of parameter fields to prevent XSS attacks.

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
Crx Content Package DeployerApplication
Affected:<= 1.9

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. Identify installed plugin version
    Navigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'CRX Content Package Deployer' or 'crx-content-package-deployer'. Check the Version column to see if it shows 1.9 or earlier.
    Affected if The installed version is 1.9 or lower (e.g., 1.9, 1.8, 1.7, etc.)
  2. Locate CRX Content Package Choice parameters in job configurations
    Review each Jenkins job configuration that uses the CRX Content Package Deployer plugin. Go to each job > Configure > look for parameters of type 'CRX Content Package Choice' in the parameter section.
    Affected if The job has one or more CRX Content Package Choice parameters configured with non-empty name or description fields
  3. Examine parameter field values
    In the job configuration page, inspect the 'Name' and 'Description' fields of each CRX Content Package Choice parameter. Look for any HTML, JavaScript, or special characters that were entered.
    Affected if The name or description fields contain user-supplied values that could include script tags or HTML markup (the plugin does not escape these before rendering)
  4. Verify parameter view page rendering
    Navigate to a job's parameter page (such as a build with parameters) and view the rendered CRX Content Package Choice parameters. Right-click and 'View Page Source' to examine how the name and description are rendered in HTML.
    Affected if The rendered HTML shows unescaped content from the parameter name or description fields, indicating the XSS vulnerability is present

A user is affected if the CRX Content Package Deployer plugin version is 1.9 or earlier AND CRX Content Package Choice parameters with name/description fields are configured in any job.

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.9
Interim mitigation

Upgrade to Jenkins CRX Content Package Deployer Plugin version 1.10 or later which includes proper escaping of parameter fields to prevent XSS attacks.

Recommended fix High confidence

Version 1.10 or later

  1. Navigate to the Jenkins dashboard
  2. Go to Manage Jenkins > Manage Plugins
  3. Locate the 'CRX Content Package Deployer' plugin in the 'Installed' tab
  4. Check the current version of the plugin
  5. If the installed version is 1.9 or earlier, click 'Update now' to upgrade to the latest available version
  6. Alternatively, download the latest version of the plugin from the Jenkins plugin repository
  7. Restart Jenkins if required after the update

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

Fix this in Crx Content Package Deployer Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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