CVE-2017-1000108: Jenkins Pipeline: Input Step Plugin

CVE-2017-1000108 · Severity: low · CVSS 3 · Published 2022-05-17

Jenkins Pipeline: Input Step Plugin

Technologies: org.jenkins-ci.plugins:pipeline-input-step (Maven). Vendors: Maven.

Quick answers

Is CVE-2017-1000108 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2017-1000108 being exploited in the wild.
How severe is CVE-2017-1000108?
Low severity, with a CVSS score of 3, published 17 May 2022.
Which products and versions are affected?
org.jenkins-ci.plugins:pipeline-input-step (Maven) ECOSYSTEM:introduced=0,fixed=2.7.
Is there a fix for CVE-2017-1000108?
Yes. org.jenkins-ci.plugins:pipeline-input-step (Maven): upgrade to 2.7 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2017-1000108?
Check whether you run org.jenkins-ci.plugins:pipeline-input-step (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • org.jenkins-ci.plugins:pipeline-input-step (Maven): upgrade to 2.7 or later
    # set org.jenkins-ci.plugins:pipeline-input-step to 2.7 in your pom.xml or build.gradle

Affected products

  • org.jenkins-ci.plugins:pipeline-input-step (Maven) ECOSYSTEM:introduced=0,fixed=2.7

Identifiers

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

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.