dbcve.org
Promoted BuildsApplication · Jenkins

CVE-2022-29045

MEDIUM · 5.4 CVSS v3.1 Published 2022-04-12
Fix available
A fix is available. Upgrade to 3.10.1 / 876.v99d29788b_36b_ 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 promoted builds Plugin 873.v6149db_d64130 and earlier, except 3.10.1, does not escape the name and description of Promoted Build 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 promoted builds Plugin fails to properly escape the name and description of Promoted Build parameters on parameter display views, resulting in a stored cross-site scripting (XSS) vulnerability. Attackers with Item/Configure permission can inject malicious script content into parameter names or descriptions that execute in the browsers of users who view these parameters.

MitigationUpgrade Jenkins promoted builds Plugin to version 3.10.1 or later, which includes proper output encoding for parameter names and descriptions.

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
Promoted BuildsApplication
Affected:< 3.10.1>= 867.v7c3a_b_83a_eb_79, < 876.v99d29788b_36b_

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 Promoted Builds Plugin is installed
    In Jenkins, go to Manage Jenkins > Manage Plugins > Installed tab, or check the file system for the plugin JAR in $JENKINS_HOME/plugins/promoted-builds/ directory. You can also use the Jenkins CLI: java -jar jenkins-cli.jar list-plugins | grep -i promoted
    Affected if The plugin is installed and the installed version is less than 3.10.1 OR falls within the range 867.v7c3a_b_83a_eb_79 to 876.v99d29788b_36b_ (exclusive)
  2. Identify jobs using Promoted Build parameters
    Search job configurations for <promotedBuildParameter> elements or look for jobs with Promotion processes configured that include parameters with custom names or descriptions. Use Jenkins script console or search configuration XML files in $JENKINS_HOME/jobs/ for <parameterDefinitions> within <actions> containing 'promoted'
    Affected if Any job configuration contains Promoted Build parameters with custom parameter names or descriptions that could contain injected script content
  3. Review who has Item/Configure permission
    Check job-level or matrix permissions in Jenkins > Manage Jenkins > Manage Users and folder/job ACLs. Look for users or groups granted Item/Configure or Job/Configure permission on jobs using Promoted Build parameters
    Affected if Users without full administrative trust have Item/Configure permission on jobs that use Promoted Build parameters

You are affected if the Promoted Builds Plugin version is less than 3.10.1 (or between 867.v7c3a_b_83a_eb_79 and 876.v99d29788b_36b_) AND any job uses Promoted Build parameters with custom names/descriptions AND untrusted users have configure permission on 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.10.1 / 876.v99d29788b_36b_ or later
Fixed in 3.10.1876.v99d29788b_36b_
Interim mitigation

Upgrade Jenkins promoted builds Plugin to version 3.10.1 or later, which includes proper output encoding for parameter names and descriptions.

Recommended fix High confidence

Promoted Builds plugin version 876.v99d29788b_36b_ (or latest stable, minimum 3.10.1)

  1. 1. Back up Jenkins configuration and job definitions
  2. 2. In Jenkins, go to Manage Jenkins > Manage Plugins
  3. 3. Go to the 'Installed' tab and locate the 'Promoted Builds' plugin
  4. 4. If a newer version is available, click 'Update' or install version 876.v99d29788b_36b_ (or the latest available version)
  5. 5. Restart Jenkins to apply the plugin update
  6. 6. Verify the plugin version is now 3.10.1 or higher / 876.v99d29788b_36b_ or higher
  7. 7. Test that promoted builds with parameters display correctly without XSS issues

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

Fix this in Promoted Builds Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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