CVE-2018-1000997: Improper Limitation of a Pathname to a Restricted Directory in Jenkins

Quick answers

Is CVE-2018-1000997 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2018-1000997 being exploited in the wild.

How severe is CVE-2018-1000997?

Low severity, with a CVSS score of 3, published 14 May 2022.

Which products and versions are affected?

org.jenkins-ci.main:jenkins-core (Maven) ECOSYSTEM:introduced=0,fixed=2.138.2; org.kohsuke.stapler:stapler-parent (Maven) ECOSYSTEM:introduced=0,fixed=1.250.2.

Is there a fix for CVE-2018-1000997?

Yes. org.jenkins-ci.main:jenkins-core (Maven): upgrade to 2.138.2 or later; org.kohsuke.stapler:stapler-parent (Maven): upgrade to 1.250.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Am I affected by CVE-2018-1000997?

Check whether you run org.jenkins-ci.main:jenkins-core (Maven) or org.kohsuke.stapler:stapler-parent (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.main:jenkins-core (Maven): upgrade to 2.138.2 or later

  # set org.jenkins-ci.main:jenkins-core to 2.138.2 in your pom.xml or build.gradle

• org.kohsuke.stapler:stapler-parent (Maven): upgrade to 1.250.2 or later

  # set org.kohsuke.stapler:stapler-parent to 1.250.2 in your pom.xml or build.gradle

Affected products

• org.jenkins-ci.main:jenkins-core (Maven) ECOSYSTEM:introduced=0,fixed=2.138.2
• org.kohsuke.stapler:stapler-parent (Maven) ECOSYSTEM:introduced=0,fixed=1.250.2

Identifiers

• CVE-2018-1000997
• GHSA-5hfp-964w-5vgm