Skip to content

Arbitrary file write vulnerability in Jenkins Pipeline: Input Step Plugin

High severity GitHub Reviewed Published Jun 24, 2022 to the GitHub Advisory Database • Updated Jan 31, 2023

Package

maven org.jenkins-ci.plugins:pipeline-input-step (Maven)

Affected versions

< 449.v77f0e8b

Patched versions

449.v77f0e8b

Description

Pipeline: Input Step Plugin 448.v37cea_9a_10a_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.

References

Published by the National Vulnerability Database Jun 23, 2022
Published to the GitHub Advisory Database Jun 24, 2022
Reviewed Jul 5, 2022
Last updated Jan 31, 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
None
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:N/S:U/C:H/I:H/A:H

EPSS score

0.084%
(38th percentile)

Weaknesses

CVE ID

CVE-2022-34177

GHSA ID

GHSA-29q6-p2cg-4v23

Source code

Credits

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