CVE-2022-34177

What it is

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 directory, allowing attackers able to configure Pipelines to create or replace arbitrary files on the Jenkins controller file system with attacker-specified content.

At a glance

Exploitability

Can be exploited over the network without logging in. High risk of data tampering.

Exploit odds

1.7% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2022-06-23 17:15 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 04:49 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 1.7% in the next 30 days (EPSS).
• Severity: 7.5 HIGH (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2022-06-23 17:15 UTC

Last modified

2026-06-17 04:49 UTC

Exploit probability

1.7% · EPSS, next 30 days

Weakness

CWE-22 · Path traversal

Record status

Modified

Affected

• Jenkins pipeline\ ≤ 448.v37cea_9a_10a_70

Attack profile CVSS 3.1 · 7.5

Attack vector

Network

Complexity

Low

Privileges needed

None

User interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

High

Availability

None

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2022-34177.md and follow it. Check whether this project is affected by CVE-2022-34177. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge