Promotion names in Jenkins promoted builds Plugin are not validated when using Job DSL

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

8.0 · CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H

EPSS

• CVE-2022-29049: 0.82% estimated exploitation activity in the next 30 days; percentile 57.13 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Jenkins promoted builds Plugin provides dedicated support for defining promotions using Job DSL Plugin. promoted builds Plugin 873.v6149dbd64130 and earlier does not validate the names of promotions defined in Job DSL. This allows attackers with Job/Configure permission to create a promotion with an unsafe name. As a result, the promotion name could be used for cross-site scripting (XSS) or to replace other config.xml files. promoted builds Plugin 876.v99d29788b36b and 3.10.1 validates the name of promotions.

Published by the source

13 Apr 2022, 00:00 UTC

Last modified by the source

21 Jul 2023, 19:28 UTC

Source last checked

26 Oct 2026, 16:11 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-jmxr-w2jc-qp7w

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2022-29049

Advisory: Promotion names in Jenkins promoted builds Plugin are not validated when using Job DSL
IDs: CVE-2022-29049, GHSA-jmxr-w2jc-qp7w
Record: https://patchnext.com/advisories/cve-2022-29049 (revision 1, source checked 26 Oct 2026, 16:11 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.0)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.jenkins-ci.plugins:promoted-builds 876.v99d29788b, 3.10.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.jenkins-ci.plugins:promoted-builds: affected < 3.10.1; >= 3.11, < 876.v99d29788b; fixed in 3.10.1, 876.v99d29788b

## Suggested inspection (read-only)
- Maven org.jenkins-ci.plugins:promoted-builds: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.jenkins-ci.plugins:promoted-builds.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-jmxr-w2jc-qp7w (GitHub-reviewed advisory GHSA-jmxr-w2jc-qp7w lists affected ranges: Maven org.jenkins-ci.plugins:promoted-builds >=0 =3.11 <876.v99d29788b)

Commands are suggestions: review each one before running it.