JenkinsApplication
CVE-2018-1000864
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA denial of service vulnerability in Jenkins CronTab.java allows authenticated users with Overall/Read permission to trigger an infinite loop in request handling threads by providing specially crafted cron expressions, causing the affected thread to hang and leading to service degradation.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
JenkinsApplication
<= 2.138.3<= 2.153
Openshift Container PlatformApplication
= 3.11CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Jenkins versionNavigate to Manage Jenkins > About Jenkins (or access /about endpoint), or run: java -jar jenkins.war --versionAffected if Version is 2.138.3 or lower, or between 2.139.0 and 2.153 inclusive, or the exact version cannot be determined (assume affected)
-
Check authorization strategyGo to Manage Jenkins > Configure Global Security > Authorization. Identify if 'Logged-in users can do anything', 'Matrix-based security', or any configuration allows unauthenticated or low-privilege users Overall/Read permission.Affected if Users with only Overall/Read permission (no admin rights) can access the system, as the vulnerability is exploitable by any authenticated user with read access
-
Identify users with Overall/Read permissionIn matrix-based security, review each user/group row in the authorization matrix. Ensure only trusted users have the Overall/Read checkbox enabled.Affected if Untrusted or anonymous users have Overall/Read permission enabled
-
Assess cron trigger exposureReview configured jobs (Manage Jenkins > Manage Views > All) and look for triggers using cron syntax (poll SCM, build periodically). Check if external users can configure job triggers.Affected if Jobs with cron triggers exist and are configurable by users with Overall/Read permission, as the vulnerability lies in CronTab.java parsing of cron expressions
You are affected if your Jenkins version falls within 2.138.3 or lower, or 2.139.0 through 2.153, AND any user with only Overall/Read permission (authenticated or anonymous) can submit cron expressions to the system.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade Jenkins to version 2.154 or LTS 2.139.4 or later to patch the vulnerable CronTab.java code; alternatively, restrict Overall/Read permission to trusted users only until patching is possible.
Fix this in Jenkins
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-1000864 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2018-1000864 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data