Skip to content
Fencer Intel
medium 6.5

CVE-2018-1000406 json

Path Traversal in Jenkins

published 7y ago modified 4mo ago also GHSA-3pr8-rf62-g893 , EUVD-2022-2226

cvss
6.5
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
4.0%
EPSS 4.0% chance of exploitation in 30 days, percentile 90%
public exploits
0
none known

Summary

A path traversal vulnerability exists in Jenkins 2.145 and earlier, LTS 2.138.1 and earlier in core/src/main/java/hudson/model/FileParameterValue.java that allows attackers with Job/Configure permission to define a file parameter with a file name outside the intended directory, resulting in an arbitrary file write on the Jenkins master when scheduling a build.

Patch / fix

  • maven org.jenkins-ci.main:jenkins-core 2.138.2, 2.146
  • cri-o openshift 3.11 1.11.10-1.rhaos3.11.git42c86f0.el7
  • kibana openshift 3.11 5.6.13-1.el7
  • jenkins openshift 3.11 2.138.2.1542054911-1.el7
  • prometheus openshift 3.11 3.11.51-1.git.5023.0ad933c.el7
  • atomic-openshift openshift 3.11 3.11.51-1.git.0.1560686.el7
  • jenkins-2-plugins openshift 3.11 3.11.1542061886-1.el7
  • openshift-ansible openshift 3.11 3.11.51-2.git.0.51c90a3.el7
  • atomic-openshift-pod openshift 3.11 3.11.51-1.git.0.1560686.el7

red hat advisories RHBA-2018:3743

Is CVE-2018-1000406 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2018-1000406 updated cvss 6.5

jenkins: Arbitrary file write vulnerability using file parameter definitions

  • Red Hat OpenShift Container Platform 3.4 jenkins Red Hat OpenShift Container Platform 3.5 jenkins Red Hat OpenShift Container Platform 3.6 jenkins Red Hat OpenShift Container Platform 3.7 jenkins Red Hat OpenShift Container Platform 3.9 jenkins Red Hat OpenShift Container Platform 3.10 jenkins
    affected: no fix planned “Will not fix”
  • Red Hat OpenShift Container Platform 3.11 kibana 5.6.13-1.el7, jenkins 2.138.2.1542054911-1.el7, jenkins-2-plugins 3.11.1542061886-1.el7, cri-o 1.11.10-1.rhaos3.11.git42c86f0.el7, prometheus 3.11.51-1.git.5023.0ad933c.el7, atomic-openshift 3.11.51-1.git.0.1560686.el7, +35 more
    fixed: vendor fix RHBA-2018:3743
  • Red Hat OpenShift Container Platform 4 jenkins
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

4.02% chance of exploitation in the next 30 days, higher than 90% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.0 6.5 CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
NVD 2.0 4.0 AV:N/AC:L/Au:S/C:N/I:P/A:N
GitHub 3.0 6.5 CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

Affected packages

ecosystem package affected fixed in
maven org.jenkins-ci.main:jenkins-core
<2.138.2
>=2.140, <2.146
2.138.2
2.146

Classification

Weakness
  • CWE-22 Improper Limitation of a Pathname to a Restricted Directory
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.