CVE-2022-29049

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

Jenkins promoted builds Plugin provides dedicated support for defining promotions using Job DSL Plugin.

promoted builds Plugin 873.v6149db_d64130 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.v99d29788b_36b_ and 3.10.1 validates the name of promotions.

The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths. Typical impact: varies by context: data corruption, logic bypass, or denial of service.

CVE-2022-29049 has a CVSS score of 8.0 (High). The vector is network-reachable, low privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (3.10.1, 876.v99d29788b); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

1. What is CVE-2022-29049? CVE-2022-29049 is a high-severity improper input validation vulnerability in org.jenkins-ci.plugins:promoted-builds (maven), affecting versions < 3.10.1. It is fixed in 3.10.1, 876.v99d29788b. The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths.
2. How severe is CVE-2022-29049? CVE-2022-29049 has a CVSS score of 8.0 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of org.jenkins-ci.plugins:promoted-builds are affected by CVE-2022-29049? org.jenkins-ci.plugins:promoted-builds (maven) versions < 3.10.1 is affected.
4. Is there a fix for CVE-2022-29049? Yes. CVE-2022-29049 is fixed in 3.10.1, 876.v99d29788b. Upgrade to this version or later.
5. Is CVE-2022-29049 exploitable, and should I be worried? Whether CVE-2022-29049 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2022-29049 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2022-29049?
   • Upgrade org.jenkins-ci.plugins:promoted-builds to 3.10.1 or later
   • Upgrade org.jenkins-ci.plugins:promoted-builds to 876.v99d29788b or later

Other vulnerabilities in org.jenkins-ci.plugins:promoted-builds