Skip to content
Fencer Intel
medium 6.5

CVE-2018-1999044 json

Infinite Loop in Jenkins Core

published 8y ago modified 4mo ago also GHSA-8qpf-fv36-h4r8 , EUVD-2022-3216

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

Summary

A denial of service vulnerability exists in Jenkins 2.137 and earlier, 2.121.2 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

Is CVE-2018-1999044 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-1999044 updated cvss 4.3

jenkins: Cron expression form validation could enter infinite loop, potentially resulting in denial of service

  • 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
    +3 more products
    Red Hat OpenShift Container Platform 3.9 jenkins Red Hat OpenShift Container Platform 3.10 jenkins Red Hat OpenShift Enterprise 3.1 jenkins
    affected: no fix planned “Will not fix”
  • Red Hat OpenShift Container Platform 3.11 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

1.17% chance of exploitation in the next 30 days, higher than 67% 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
2.138

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.