Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

Maven package

org.jenkins-ci.plugins:pipeline-input-step

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. High, CVSS 8.8MavenPublished

    Arbitrary file write vulnerability in Jenkins Pipeline: Input Step Plugin

    CVE-2022-34177 · GHSA-29q6-p2cg-4v23

    Affected
    • Maven org.jenkins-ci.plugins:pipeline-input-step < 449.v77f0e8b
    Fixed in
    449.v77f0e8b· Vendor fix available
    Issue
    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.

    Recommended action: Upgrade to 449.v77f0e8b (pre-release) or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  2. High, CVSS 7.5MavenPublished

    Jenkins Pipeline: Input Step Plugin

    CVE-2017-1000108 · GHSA-hxpw-7x95-q38m

    Affected
    • Maven org.jenkins-ci.plugins:pipeline-input-step < 2.7
    Fixed in
    2.7· Vendor fix available
    Issue
    The Pipeline: Input Step Plugin by default allowed users with Item/Read access to a pipeline to interact with the step to provide input. This has been changed, and now requires users to have the Item/Build permission instead.

    Recommended action: Upgrade to 2.7 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →