dbcve.org
JiraApplication · Jenkins

CVE-2022-29041

MEDIUM · 5.4 CVSS v3.1 Published 2022-04-12
Fix available
A fix is available. Upgrade to 3.6.1 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 Jira Plugin 3.7 and earlier, except 3.6.1, does not escape the name and description of Jira Issue and Jira Release Version 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 Jira Plugin versions 3.7 and earlier (except 3.6.1) fails to properly escape the name and description fields of Jira Issue and Jira Release Version parameters when rendering them in parameter views. This allows an attacker with Item/Configure permission to inject malicious JavaScript code that executes in the browsers of other users viewing these parameters, leading to stored cross-site scripting (XSS).

MitigationUpgrade Jenkins Jira Plugin to version 3.6.1 or later. As a compensating control, restrict Item/Configure permission to trusted users only until the upgrade 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
JiraApplication
Affected:< 3.6.1= 3.7

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 Jira Plugin version
    Navigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab, locate the Jira Plugin and check the Version column
    Affected if The installed version is 3.7 or any version below 3.6.1 (versions 3.0-3.7 are affected)
  2. Verify parameter configuration access
    Navigate to a job that uses Jira Issue or Jira Release Version parameters, then go to Configure > Parameters section to see if these parameter types are defined
    Affected if The job has Jira Issue Parameter or Jira Release Version Parameter types configured with user-supplied name or description values
  3. Check Item/Configure permission assignment
    Go to Jenkins > Manage Jenkins > Manage Users, then review which users or groups have Item/Configure permission on jobs using Jira parameters (found in job configuration under Matrix-based security or Project-based authentication)
    Affected if Users who are not fully trusted have Item/Configure permission on jobs that use the affected Jira parameter types

You are affected if the Jira Plugin version is 3.7 or below 3.6.1 AND your jobs use Jira Issue or Jira Release Version parameters AND untrusted users have Item/Configure permission to configure those jobs.

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 3.6.1 or later
Fixed in 3.6.1
Interim mitigation

Upgrade Jenkins Jira Plugin to version 3.6.1 or later. As a compensating control, restrict Item/Configure permission to trusted users only until the upgrade can be applied.

Recommended fix High confidence

Jira Plugin version 3.6.1 or later

  1. 1. Navigate to Jenkins dashboard
  2. 2. Go to Manage Jenkins > Manage Plugins
  3. 3. Click on the 'Installed' tab
  4. 4. Locate the Jira Plugin in the list
  5. 5. If an upgrade is available, click 'Upgrade' button next to the Jira Plugin
  6. 6. Alternatively, download the Jira Plugin version 3.6.1 or later from the Jenkins plugin repository
  7. 7. Go to Manage Jenkins > Manage Plugins > Advanced
  8. 8. Under 'Upload Plugin', upload the new .hpi file

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

Fix this in Jira Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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