CVE-2022-34177: Pipeline input step Input Step Plugin Vulnerability
HIGHCVE-2022-34177 is a HIGH (CVSS 8.8) input step plugin vulnerability (CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')) affecting Pipeline input step libraries in the Maven ecosystem. The issue involves input step plugin. Remediation is available by upgrading affected packages to version 449.v77f0e8b.
CVE-2022-34177 at a Glance
Security Impact
CVSS: 8.8
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H).
How to Fix CVE-2022-34177
To remediate this vulnerability, upgrade all affected Pipeline input step dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
<dependency>
<groupId>org.jenkins-ci.plugins</groupId>
<artifactId>pipeline-input-step</artifactId>
<version>449.v77f0e8b</version>
</dependency>
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
mvn dependency:tree -Dincludes=org.jenkins-ci.plugins
How to Check if You Are Affected
To determine whether your Java application is affected by CVE-2022-34177, inspect your build dependencies using the Maven Dependency Plugin:
mvn dependency:tree -Dincludes=org.jenkins-ci.plugins
Analyze the terminal output to locate any version of Pipeline input step in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 449.v77f0e8b), your application is affected.
Note: The mvn dependency:tree -Dincludes=org.jenkins-ci.plugins command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal'), where the product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. In Pipeline input step, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2022-34177 Affected Pipeline input step Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
org.jenkins-ci.plugins:pipeline-input-step
|
Maven |
< 449.v77f0e8b
|
449.v77f0e8b
|
References
Frequently Asked Questions
What is CVE-2022-34177?
Which Pipeline input step versions are affected?
What version fixes CVE-2022-34177?
Is pipeline-input-step affected?
What is the CVSS score of CVE-2022-34177?
What CWE is associated with CVE-2022-34177?
How can I check Maven dependencies for CVE-2022-34177?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-29q6-p2cg-4v23",
"modified" : "2022-12-05T23:27:46Z",
"published" : "2022-06-24T00:00:31Z",
"aliases" : [ "CVE-2022-34177" ],
"summary" : "Arbitrary file write vulnerability in Jenkins Pipeline: Input Step Plugin",
"details" : "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.\n\nThis allows attackers able to configure Pipelines to create or replace arbitrary files on the Jenkins controller file system with attacker-specified content.\n\nPipeline: Input Step Plugin 449.v77f0e8b_845c4 prohibits use of `file` parameters for Pipeline `input` steps. Attempts to use them will fail Pipeline execution.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Maven",
"name" : "org.jenkins-ci.plugins:pipeline-input-step"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "449.v77f0e8b"
} ]
} ]
} ],
"references" : [ {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2022-34177"
}, {
"type" : "WEB",
"url" : "https://github.com/jenkinsci/pipeline-input-step-plugin/commit/77f0e8b845c4ad429f6c717eab21cf4e7a69168e"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/jenkinsci/pipeline-input-step-plugin"
}, {
"type" : "WEB",
"url" : "https://www.jenkins.io/security/advisory/2022-06-22/#SECURITY-2705"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-22" ],
"severity" : "HIGH",
"github_reviewed" : true,
"github_reviewed_at" : "2022-07-05T22:56:27Z",
"nvd_published_at" : "2022-06-23T17:15:00Z"
}
}