dbcve.org
CvsApplication · Jenkins

CVE-2022-29037

MEDIUM · 5.4 CVSS v3.1 Published 2022-04-12
Fix available
A fix is available. Upgrade to after 2.19 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 CVS Plugin 2.19 and earlier does not escape the name and description of CVS Symbolic Name 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 CVS Plugin versions 2.19 and earlier does not escape the name and description fields of CVS Symbolic Name parameters when rendering them in parameter display views, allowing authenticated users with Item/Configure permission to inject malicious JavaScript that executes in the browsers of other users viewing these parameters (stored XSS).

MitigationUpgrade the Jenkins CVS Plugin to version 2.20 or later which includes proper escaping of parameter fields. Alternatively, restrict Item/Configure permission to trusted users only until the upgrade can be completed.

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
CvsApplication
Affected:<= 2.19

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 Jenkins CVS Plugin is installed
    Navigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'CVS' or check the CVS Plugin version in the plugin's details pane
    Affected if CVS Plugin version is 2.19 or earlier, or the plugin is installed but version cannot be determined (assume affected)
  2. Confirm CVS Symbolic Name parameters are in use
    Review configured jobs that use CVS with parameterized builds, specifically looking for 'CVS Symbolic Name' parameter type in the job configuration
    Affected if Any job has CVS Symbolic Name parameters configured with user-supplied name or description values
  3. Identify users with Item/Configure permission
    Navigate to Manage Jenkins > Manage and Assign Roles > Assign Roles, or review folder/project-based permissions to list users or groups granted Configure permission on jobs using CVS parameters
    Affected if Users other than trusted administrators have Item/Configure permission on jobs using CVS Symbolic Name parameters

You are affected if the CVS Plugin version is 2.19 or earlier AND CVS Symbolic Name parameters are configured on any job, regardless of who has permission, since the XSS triggers when other users view those parameters.

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 2.19
Interim mitigation

Upgrade the Jenkins CVS Plugin to version 2.20 or later which includes proper escaping of parameter fields. Alternatively, restrict Item/Configure permission to trusted users only until the upgrade can be completed.

Recommended fix Moderate confidence

CVS Plugin version 2.20 or later

  1. Navigate to Jenkins > Manage Jenkins > Manage Plugins
  2. Go to the 'Installed' tab and locate the CVS Plugin
  3. If an update is available, select the CVS Plugin and click 'Download now and install after restart'
  4. Alternatively, check the 'Updates' tab for CVS Plugin version 2.20 or later
  5. Restart Jenkins after the plugin update completes
  6. Verify the plugin version is 2.20 or later under Manage Plugins > Installed

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

Fix this in Cvs Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
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,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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