Skip to content
Fencer Intel
medium 6.5

CVE-2018-1000864 json

Loop with Unreachable Exit Condition in Jenkins

published 7y ago modified 4mo ago also GHSA-9cjv-93g7-c6mv , EUVD-2022-3354

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

Summary

A denial of service vulnerability exists in Jenkins 2.153 and earlier, LTS 2.138.3 and earlier in CronTab.java that allows attackers with Overall/Read permission to have a request handling thread enter an infinite loop.

Patch / fix

  • maven org.jenkins-ci.main:jenkins-core 2.138.4, 2.154
  • jenkins openshift 3.11 2.138.4.1544416383-1.el7

red hat advisories RHBA-2019:0024

Is CVE-2018-1000864 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-1000864 updated cvss 7.5

jenkins: potential denial of service through cron expression form validation (SECURITY-1193)

  • Red Hat OpenShift Container Platform 3.2 jenkins Red Hat OpenShift Container Platform 3.3 jenkins 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
    +2 more products
    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 jenkins 2.138.4.1544416383-1.el7
    fixed: vendor fix RHBA-2019:0024
  • Red Hat OpenShift Container Platform 3.11 python-elasticsearch 5.4.0-1.el7, ansible-service-broker 1.3.21-1.el7, automation-broker-apb-role 1.3.21-1.el7, prometheus 3.11.59-1.git.5023.748e6f7.el7, ansible-service-broker-selinux 1.3.21-1.el7, atomic-openshift 3.11.59-1.git.0.7cb6277.el7, +34 more
    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

2.75% chance of exploitation in the next 30 days, higher than 86% 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:N/A:H
NVD 2.0 4.0 AV:N/AC:L/Au:S/C:N/I:N/A:P
GitHub 3.0 6.5 CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Affected packages

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

Classification

Weakness
  • CWE-835 Loop with Unreachable Exit Condition
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.