dbcve.org
Gerrit TriggerApplication · Jenkins

CVE-2022-29039

MEDIUM · 5.4 CVSS v3.1 Published 2022-04-12
Fix available
A fix is available. Upgrade to after 2.35.2 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 Gerrit Trigger Plugin 2.35.2 and earlier does not escape the name and description of Base64 Encoded String 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 Gerrit Trigger Plugin fails to properly escape the name and description fields of Base64 Encoded String parameters before rendering them in web views, allowing injection of malicious script. An attacker with Item/Configure permission can embed XSS payloads into these parameter fields that execute when other users view the affected pages.

MitigationUpgrade the Gerrit Trigger Plugin to version 2.35.3 or later which includes proper output encoding for Base64 Encoded String parameter fields.

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
Gerrit TriggerApplication
Affected:<= 2.35.2

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 Gerrit Trigger plugin is installed
    Navigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'Gerrit Trigger' in the list of installed plugins.
    Affected if The Gerrit Trigger plugin is not found in the installed plugins list.
  2. Check installed plugin version
    In the plugin management interface, locate the Gerrit Trigger plugin and note the version number displayed. Compare this against the affected range: any version <= 2.35.2 is vulnerable.
    Affected if The installed version is 2.35.2 or lower.
  3. Identify Base64 Encoded String parameters in job configurations
    Review configured jobs that use the Gerrit Trigger plugin. For each job, go to Configure > Gerrit Trigger section and expand parameter sections. Look for parameters of type 'Base64 Encoded String' and inspect their Name and Description fields.
    Affected if Any job contains a Base64 Encoded String parameter with unescaped content in the Name or Description field.
  4. Audit Item/Configure permission assignments
    Navigate to Manage Jenkins > Manage and Assign Permissions. Review which users or groups have Item/Configure permission, as this permission level is required to inject malicious payloads.
    Affected if Users with Item/Configure permission exist and the plugin version is vulnerable.

The environment is affected if the Gerrit Trigger plugin version is 2.35.2 or lower and there are Base64 Encoded String parameters configured in any job, particularly accessible to users with Item/Configure permission.

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

Upgrade the Gerrit Trigger Plugin to version 2.35.3 or later which includes proper output encoding for Base64 Encoded String parameter fields.

Recommended fix High confidence

Gerrit Trigger 2.35.3 or later

  1. Navigate to the Jenkins dashboard
  2. Go to Manage Jenkins > Manage Plugins
  3. Click on the 'Installed' tab
  4. Locate the 'Gerrit Trigger' plugin in the list
  5. If an update is available, check the plugin and click 'Update'
  6. Restart Jenkins to apply the changes

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

Fix this in Gerrit Trigger Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,820
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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