Skip to content
Fencer Intel
medium 5.5

CVE-2018-8017 json

Comparison errorr in org.apache.tika:tika-core

published 2018-09-19 8 y ago modified 2026-06-17 4 mo ago also GHSA-j53j-gmr9-h8g3 , EUVD-2018-0623

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

Summary

In Apache Tika 1.2 to 1.18, a carefully crafted file can trigger an infinite loop in the IptcAnpaParser.

Patch / fix

  • maven org.apache.tika:tika-core 1.19
  • tika Debian 11 1.20-1

debian advisories DEBIAN-CVE-2018-8017

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-8017 updated cvss 2.5

tika: infinite loop in the IptcAnpaParser

  • Red Hat BPM Suite 6 tika-core Red Hat JBoss BRMS 5 tika-core Red Hat JBoss BRMS 6 tika-core Red Hat JBoss Data Virtualization 6 tika-core
    affected: no fix planned “Will not fix”
  • Red Hat JBoss Fuse Integration Service 2 tika-core
    affected: no fix planned “Out of support scope”
  • 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
    affected: no fix planned “Will not fix”
  • Red Hat Fuse 7 camel-tika camel-tika Red Hat Satellite 5 tika
    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.28% chance of exploitation in the next 30 days, higher than 83% 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-core
>=1.2, <1.19
1.19

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.