dbcve.org
Promoted BuildsApplication · Jenkins

CVE-2022-29049

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 validate the names of promotions defined in Job DSL, allowing attackers with Job/Configure permission to create a promotion with an unsafe name.

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 validate promotion names defined in Job DSL, allowing authenticated users with Job/Configure permission to create promotions with unsafe names that could lead to security compromise.

MitigationUpgrade Jenkins promoted builds Plugin to version 3.10.1 or later which includes proper validation of promotion names in Job DSL definitions.

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
    Navigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'Promoted Builds', or check the plugin file at $JENKINS_HOME/plugins/promoted-builds/META-INF/MANIFEST.MF for the Version attribute
    Affected if Plugin is not present in the Jenkins instance
  2. Determine the installed plugin version
    In Manage Jenkins > Manage Plugins > Installed, find the Promoted Builds plugin and note the Version column; alternatively, read the Version from the MANIFEST.MF file
    Affected if Unable to determine the version number for comparison
  3. Compare installed version against vulnerable ranges
    Check if the installed version is less than 3.10.1 OR falls in the range 867.v7c3a_b_83a_eb_79 through 876.v99d29788b_36b_ (exclusive of 876.v99d29788b_36b_)
    Affected if Version is < 3.10.1 OR (version >= 867.v7c3a_b_83a_eb_79 AND version < 876.v99d29788b_36b_)
  4. Confirm Job DSL usage for promotions
    Search job configuration files (config.xml) or Job DSL scripts for 'promotions' blocks or PromotionProcess definitions created via Job DSL rather than the UI
    Affected if Promotions are defined via Job DSL scripts in the environment

A user is affected if the Promoted Builds plugin is installed at a vulnerable version AND promotions are defined or configurable via Job DSL with users having Job/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 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 validation of promotion names in Job DSL definitions.

Recommended fix High confidence

Promoted Builds plugin version 876.v99d29788b_36b_ (or 3.10.1)

  1. 1. Backup your Jenkins configuration and plugins directory.
  2. 2. Navigate to Manage Jenkins > Manage Plugins.
  3. 3. Go to the 'Installed' tab and locate the 'Promoted Builds' plugin.
  4. 4. If automatic updates are enabled, check for updates and install the latest version.
  5. 5. Alternatively, download the Promoted Builds plugin version 876.v99d29788b_36b_ (or 3.10.1) from the Jenkins plugin repository.
  6. 6. Restart Jenkins to apply the plugin update.
  7. 7. Verify the plugin version after restart in Manage Plugins > Installed.

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
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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