Skip to content
Fencer Intel
medium 5.5

CVE-2018-1339 json

org.apache.tika:tika-parsers has an Infinite Loop vulnerability

published 8y ago modified 4mo ago also GHSA-p699-3wgc-7h72 , EUVD-2018-0647

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

Summary

A carefully crafted (or fuzzed) file can trigger an infinite loop in Apache Tika's ChmParser in versions of Apache Tika before 1.18.

Patch / fix

  • maven org.apache.tika:tika-parsers 1.18
  • apache tika 1.18
  • tika Debian 11 1.18-1

debian advisories DEBIAN-CVE-2018-1339

Is CVE-2018-1339 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-1339 updated cvss 6.5

tika: Infinite loop in ChmParser can allow remote attacker to cause a denial of service

  • Red Hat JBoss BRMS 5 tika-core
    affected: no fix planned “Out of support scope”
  • Red Hat JBoss Data Virtualization 6 tika-core Red Hat Satellite 5 tika
    affected: no fix planned “Will not fix”
  • Red Hat Fuse 7
    fixed: vendor fix RHSA-2018:2669
  • Red Hat BPM Suite 6 tika-core Red Hat JBoss BRMS 6 tika-core Red Hat JBoss Fuse Integration Service 2 tika-core Red Hat JBoss Fuse Service Works 6 tika-core Red Hat Software Collections rh-eclipse46-tika, rh-eclipse46-tika-java7, rh-eclipse46-tika-javadoc, rh-eclipse46-tika-parsers, rh-eclipse46-tika-serialization
    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.56% chance of exploitation in the next 30 days, higher than 85% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

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

Affected packages

ecosystem package affected fixed in
maven org.apache.tika:tika-parsers
<1.18
1.18

Affected products

  • Apache Software Foundation Apache Tika

Classification

Weakness
  • CWE-835 Loop with Unreachable Exit Condition

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.