Maven package
org.jenkins-ci.plugins/pipeline-input-step
pkg:maven/org.jenkins-ci.plugins/pipeline-input-step
Vulnerabilities (3)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2022-43407 | — | < 456.vd8a_957db_5b_e9 | 456.vd8a_957db_5b_e9 | Oct 19, 2022 | Jenkins Pipeline: Input Step Plugin 451.vf1a_a_4f405289 and earlier does not restrict or sanitize the optionally specified ID of the 'input' step, which is used for the URLs that process user interactions for the given 'input' step (proceed or abort) and is not correctly encoded, | ||
| CVE-2022-34177 | — | < 449.v77f0e8b | 449.v77f0e8b | Jun 22, 2022 | Jenkins Pipeline: Input Step Plugin 448.v37cea_9a_10a_70 and earlier archives files uploaded for `file` parameters for Pipeline `input` steps on the controller as part of build metadata, using the parameter name without sanitization as a relative path inside a build-related direc | ||
| CVE-2017-1000108 | Hig | 7.5 | < 2.7 | 2.7 | Oct 5, 2017 | The Pipeline: Input Step Plugin by default allowed users with Item/Read access to a pipeline to interact with the step to provide input. This has been changed, and now requires users to have the Item/Build permission instead. |
- CVE-2022-43407Oct 19, 2022affected < 456.vd8a_957db_5b_e9fixed 456.vd8a_957db_5b_e9
Jenkins Pipeline: Input Step Plugin 451.vf1a_a_4f405289 and earlier does not restrict or sanitize the optionally specified ID of the 'input' step, which is used for the URLs that process user interactions for the given 'input' step (proceed or abort) and is not correctly encoded,
- CVE-2022-34177Jun 22, 2022affected < 449.v77f0e8bfixed 449.v77f0e8b
Jenkins Pipeline: Input Step Plugin 448.v37cea_9a_10a_70 and earlier archives files uploaded for `file` parameters for Pipeline `input` steps on the controller as part of build metadata, using the parameter name without sanitization as a relative path inside a build-related direc
- affected < 2.7fixed 2.7
The Pipeline: Input Step Plugin by default allowed users with Item/Read access to a pipeline to interact with the step to provide input. This has been changed, and now requires users to have the Item/Build permission instead.