Arbitrary file write vulnerability in Jenkins Pipeline: Input Step Plugin

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

8.8 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

EPSS

• CVE-2022-34177: 1.70% estimated exploitation activity in the next 30 days; percentile 77.18 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Pipeline: Input Step Plugin 448.v37cea9a10a70 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.v77f0e8b845c4 prohibits use of file parameters for Pipeline input steps. Attempts to use them will fail Pipeline execution.

Published by the source

24 Jun 2022, 00:00 UTC

Last modified by the source

31 Jan 2023, 05:02 UTC

Source last checked

26 Oct 2026, 16:05 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-29q6-p2cg-4v23

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2022-34177

Advisory: Arbitrary file write vulnerability in Jenkins Pipeline: Input Step Plugin
IDs: CVE-2022-34177, GHSA-29q6-p2cg-4v23
Record: https://patchnext.com/advisories/cve-2022-34177 (revision 1, source checked 26 Oct 2026, 16:05 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.jenkins-ci.plugins:pipeline-input-step 449.v77f0e8b. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.jenkins-ci.plugins:pipeline-input-step: affected < 449.v77f0e8b; fixed in 449.v77f0e8b

## Suggested inspection (read-only)
- Maven org.jenkins-ci.plugins:pipeline-input-step: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.jenkins-ci.plugins:pipeline-input-step.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-29q6-p2cg-4v23 (GitHub-reviewed advisory GHSA-29q6-p2cg-4v23 lists affected ranges: Maven org.jenkins-ci.plugins:pipeline-input-step >=0 <449.v77f0e8b)

Commands are suggestions: review each one before running it.