Vulnerabilities (CVE)

Filtered by vendor Apache Subscribe
Filtered by product Tika
Total 25 CVE
CVE Vendors Products Updated CVSS v2 CVSS v3
CVE-2018-1335 1 Apache 1 Tika 2024-11-21 9.3 HIGH 8.1 HIGH
From Apache Tika versions 1.7 to 1.17, clients could send carefully crafted headers to tika-server that could be used to inject commands into the command line of the server running tika-server. This vulnerability only affects those running tika-server on a server that is open to untrusted clients. The mitigation is to upgrade to Tika 1.18.
CVE-2018-17197 1 Apache 1 Tika 2024-11-21 4.3 MEDIUM 6.5 MEDIUM
A carefully crafted or corrupt sqlite file can cause an infinite loop in Apache Tika's SQLite3Parser in versions 1.8-1.19.1 of Apache Tika.
CVE-2018-11796 1 Apache 1 Tika 2024-11-21 5.0 MEDIUM 7.5 HIGH
In Apache Tika 1.19 (CVE-2018-11761), we added an entity expansion limit for XML parsing. However, Tika reuses SAXParsers and calls reset() after each parse, which, for Xerces2 parsers, as per the documentation, removes the user-specified SecurityManager and thus removes entity expansion limits after the first parse. Apache Tika versions from 0.1 to 1.19 are therefore still vulnerable to entity expansions which can lead to a denial of service attack. Users should upgrade to 1.19.1 or later.
CVE-2018-11762 1 Apache 1 Tika 2024-11-21 5.8 MEDIUM 5.9 MEDIUM
In Apache Tika 0.9 to 1.18, in a rare edge case where a user does not specify an extract directory on the commandline (--extract-dir=) and the input file has an embedded file with an absolute path, such as "C:/evil.bat", tika-app would overwrite that file.
CVE-2018-11761 2 Apache, Oracle 2 Tika, Business Process Management Suite 2024-11-21 5.0 MEDIUM 7.5 HIGH
In Apache Tika 0.1 to 1.18, the XML parsers were not configured to limit entity expansion. They were therefore vulnerable to an entity expansion vulnerability which can lead to a denial of service attack.