NVD / CVE Program· CNA jenkins

CVE-2022-34177: Jenkins Pipeline: Input Step Plugin 448.v37cea_9a_10a_70 and earlier archives files uploaded for `file` parameters for Pipeline `input` step

Noroxi assessment

Priority: Monitor (action score 31/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 1.6% (FIRST EPSS); higher than 77.2% of all records.
Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
Fixed version: org.jenkins-ci.plugins:pipeline-input-step (Maven) 449.v77f0e8b; jenkins-2-plugins (Red Hat:openshift:4.10::el8) 0:4.10.1663147786-1.el8; jenkins (Red Hat:openshift:4.8::el8) 0:2.361.1.1672840472-1.el8.

Low priority for now. Upgrade to org.jenkins-ci.plugins:pipeline-input-step (Maven) 449.v77f0e8b; jenkins-2-plugins (Red Hat:openshift:4.10::el8) 0:4.10.1663147786-1.el8; jenkins (Red Hat:openshift:4.8::el8) 0:2.361.1.1672840472-1.el8 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

HighCVSS 7.5 · v3.1—No exploit Fix available

Published: Jun 23, 2022
Updated: Jun 17, 2026
EPSS: 1.6% · 77th percentile
CWE: CWE-22

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 30 / 40 · 7.5 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 1 / 30 · 1.6%

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
jenkins	pipeline\	cpe:2.3:a:jenkins:pipeline\

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

jenkins pipeline: input stepup to 448.v37cea_9a_10a_70 inclusive

Versions reported by the vendor

Affected version ranges reported by the assigning authority (jenkins). Independent of NVD's CPE analysis and usually ahead of it.

Jenkins project Jenkins Pipeline: Input Step Plugin
- 447.449.v193fd29f6021, 2.12.2not affected
- unspecified and later · up to and including 448.v37cea_9a_10a_70affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Maven	org.jenkins-ci.plugins:pipeline-input-step	before 449.v77f0e8b	449.v77f0e8b
Red Hat:openshift:4.10::el8	jenkins-2-plugins	before 0:4.10.1663147786-1.el8	0:4.10.1663147786-1.el8
Red Hat:openshift:4.8::el8	jenkins	before 0:2.361.1.1672840472-1.el8	0:2.361.1.1672840472-1.el8
Red Hat:openshift:4.8::el8	jenkins-2-plugins	before 0:4.8.1672842762-1.el8	0:4.8.1672842762-1.el8
Red Hat:openshift:4.9::el8	jenkins-2-plugins	before 0:4.9.1669894222-1.el8	0:4.9.1669894222-1.el8

Same product

jenkins: all records

Other highest-scoring records for the same primary product.

CVE-2019-1003030A sandbox bypass vulnerability exists in Jenkins Pipeline: Groovy Plugin 2.63 and earlier in pom.xml, src/main/java/org/jenkinsci/plugins/woKEV
98Now
CVE-2019-1003001A sandbox bypass vulnerability exists in Pipeline: Groovy Plugin 2.61 and earlier in src/main/java/org/jenkinsci/plugins/workflow/cps/CpsFlo
61This week
CVE-2019-1003002A sandbox bypass vulnerability exists in Pipeline: Declarative Plugin 1.3.3 and earlier in pipeline-model-definition/src/main/groovy/org/jen
59Plan

Published before and after this one in the same product

← EarlierCVE-2022-29047Apr 12, 2022 · Jenkins Pipeline: Shared Groovy Libraries Plugin 564.ve62a_4eb_b_e039 and earlier, except 2.21.3, allows attackers able to submit pull reque
21Monitor
← EarlierCVE-2022-30945May 17, 2022 · Jenkins Pipeline: Groovy Plugin 2689.v434009a_31b_f1 and earlier allows loading any Groovy source files on the classpath of Jenkins and Jenk
34Monitor
Later →CVE-2022-43402Oct 19, 2022 · A sandbox bypass vulnerability involving various casts performed implicitly by the Groovy language runtime in Jenkins Pipeline: Groovy Plugi
39Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
Maven:org.jenkins-ci.plugins:pipeline-input-step	449.v77f0e8b	Package registry (OSV)
red hat:jenkins	0:2.361.1.1672840472-1.el8 · Red Hat:openshift:4.8::el8	Package registry (OSV)
red hat:jenkins-2-plugins	0:4.10.1663147786-1.el8 · Red Hat:openshift:4.10::el8	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
No account or password is required.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: none
Integrity: high · data or configuration can be modified
Availability: none

Attack vector: Network
Attack complexity: Low
Privileges required: None
User interaction: None
Scope: Unchanged
Confidentiality impact: None
Integrity impact: High
Availability impact: None

Weakness class (CWE)

CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

CVSS vector

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

nvd-primary

Root cause

A user-supplied file name is joined with the allowed directory, but the result is never checked to confirm it is still inside that directory.

The bug in code

The whole CWE-22 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1const file = path.join(ROOT, req.query.name);
2res.sendFile(file);

Fixed

1const file = path.resolve(ROOT, req.query.name);
2if (!file.startsWith(ROOT + path.sep)) {
3  return res.sendStatus(400);
4}
5res.sendFile(file);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

—

Change log

Fix✗ → ✓Sep 28, 2026, 10:47 PM UTC

For records you follow, these changes also arrive as notifications. →

References

www.jenkins.io/security/advisory/2022-06-22/#SECURITY-2705

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records