Skip to content

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

High severity GitHub Reviewed Published Apr 13, 2022 to the GitHub Advisory Database • Updated Jul 21, 2023

Package

maven org.jenkins-ci.plugins:promoted-builds (Maven)

Affected versions

< 3.10.1
>= 3.11, < 876.v99d29788b

Patched versions

3.10.1
876.v99d29788b

Description

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.

References

Published by the National Vulnerability Database Apr 12, 2022
Published to the GitHub Advisory Database Apr 13, 2022
Reviewed Apr 22, 2022
Last updated Jul 21, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H

EPSS score

0.054%
(24th percentile)

Weaknesses

CVE ID

CVE-2022-29049

GHSA ID

GHSA-jmxr-w2jc-qp7w

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.