dbcve.org
Pipeline\Application · Jenkins

CVE-2022-34177

HIGH · 7.5 CVSS v3.1 Published 2022-06-23
Fix available
A fix is available. Upgrade to after 448.v37cea_9a_10a_70 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Jenkins Pipeline: Input Step Plugin fails to sanitize parameter names when archiving uploaded files for Pipeline input steps. This path traversal vulnerability allows authenticated attackers with Pipeline configuration access to write arbitrary files to the Jenkins controller filesystem by using manipulated parameter names as relative paths.

MitigationUpdate Jenkins Pipeline: Input Step Plugin to version 448.v37cea_9a_10a_70 or later. As a compensating control, restrict Pipeline configuration permissions to trusted users only.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Pipeline\Application
Affected:<= 448.v37cea_9a_10a_70

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Pipeline: Input Step Plugin is installed
    Navigate to Manage Jenkins > Manage Plugins > Installed and search for 'Pipeline: Input Step' in the list of installed plugins
    Affected if The plugin is present in the installed plugins list
  2. Check the installed version of Pipeline: Input Step Plugin
    In the plugin manager, view the version column for the Pipeline: Input Step plugin. Compare against the affected version range: any version <= 448.v37cea_9a_10a_70 is vulnerable
    Affected if The installed version is 448.v37cea_9a_10a_70 or earlier
  3. Review Pipeline job configurations for input steps with file parameters
    Inspect Pipeline (Groovy) job configurations for usage of the 'input' step with 'file' parameters, such as 'parameters { file(...) }' or file parameter binding in input steps
    Affected if Pipelines use the input step with file parameter configuration, which triggers the vulnerable file archiving code path
  4. Audit user permissions for Pipeline configuration access
    Navigate to Manage Jenkins > Manage and Assign Permissions. Review which users or groups have Job/Configure permission on Pipeline jobs. Check if untrusted or non-admin users have Pipeline configuration access
    Affected if Users other than administrators have the ability to configure Pipeline jobs and therefore can manipulate parameter names in input steps

A user is affected if the Pipeline: Input Step Plugin version is 448.v37cea_9a_10a_70 or earlier AND untrusted users have Pipeline configuration permissions AND Pipeline jobs use input steps with file parameters.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 448.v37cea_9a_10a_70
Interim mitigation

Update Jenkins Pipeline: Input Step Plugin to version 448.v37cea_9a_10a_70 or later. As a compensating control, restrict Pipeline configuration permissions to trusted users only.

Recommended fix Moderate confidence

Pipeline Input Step Plugin version 448.v37cea_9a_10a_70 or later (check Jenkins plugin repository for latest available version)

  1. 1. Navigate to Jenkins dashboard
  2. 2. Go to Manage Jenkins > Manage Plugins
  3. 3. Click on the 'Installed' tab
  4. 4. Search for 'Pipeline: Input Step' plugin
  5. 5. If the installed version is 448.v37cea_9a_10a_70 or earlier, click 'Update' to install the latest available version
  6. 6. Restart Jenkins if required to complete the update

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Pipeline\ Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,072.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-34177 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-34177 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data