Pipeline: Input Step Plugin 448.v37cea9a10a_70 and earlier allows Pipeline authors to specify file
parameters for Pipeline input
steps even though they are unsupported. Although the uploaded file is not copied to the workspace, Jenkins archives the file on the controller as part of build metadata using the parameter name without sanitization as a relative path inside a build-related directory.
This allows attackers able to configure Pipelines to create or replace arbitrary files on the Jenkins controller file system with attacker-specified content.
Pipeline: Input Step Plugin 449.v77f0e8b_845c4 prohibits use of file
parameters for Pipeline input
steps. Attempts to use them will fail Pipeline execution.
{ "nvd_published_at": "2022-06-23T17:15:00Z", "github_reviewed_at": "2022-07-05T22:56:27Z", "severity": "HIGH", "github_reviewed": true, "cwe_ids": [ "CWE-22" ] }