Overview 8 matches · 4 protected · 1 exploited · 0 CISA KEV · 2 public PoC · 1 EPSS ≥ 0.5
Protected by Waratek
4
50.0%
Rule in development
0
0.0%
Mitigation candidate
0
0.0%
No exploit published
4
50.0%
blocked by ARMR today
4
50.0%
partly blocked
0
0.0%
not blocked
4
50.0%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
1
12.5%
Working exploit published
0
0.0%
Proof of concept only
1
12.5%
Forecast only
0
0.0%
No public exploit
6
75.0%
split by
peak 3 / month
Apr 183
Protected by Waratek1
No exploit published2
High1
Medium2
blocked by ARMR today1
not blocked2
Exploited1
No public exploit2
May 180
Jun 180
Jul 180
Aug 180
Sep 183
Protected by Waratek2
No exploit published1
High1
Medium2
blocked by ARMR today2
not blocked1
Proof of concept only1
No public exploit2
Oct 181
Protected by Waratek1
High1
blocked by ARMR today1
No public exploit1
Nov 180
Dec 181
No exploit published1
Medium1
not blocked1
No public exploit1
Apr 18May 18Jun 18Jul 18Aug 18Sep 18Oct 18Nov 18Dec 18
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2018-17197 | Medium | 2018-12-24 | No exploit published | No public exploit | 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 | High | 2018-10-09 | Protected by Waratek | No public exploit | 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-8017 | Medium | 2018-09-19 | No exploit published | No public exploit | In Apache Tika 1.2 to 1.18, a carefully crafted file can trigger an infinite loop in the IptcAnpaParser. |
| CVE-2018-11762 | Medium | 2018-09-19 | Protected by Waratek | No public exploit | 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 | High | 2018-09-19 | Protected by Waratek | Proof of concept only | 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. |
| CVE-2018-1339 | Medium | 2018-04-25 | No exploit published | No public exploit | A carefully crafted (or fuzzed) file can trigger an infinite loop in Apache Tika's ChmParser in versions of Apache Tika before 1.18. |
| CVE-2018-1338 | Medium | 2018-04-25 | No exploit published | No public exploit | A carefully crafted (or fuzzed) file can trigger an infinite loop in Apache Tika's BPGParser in versions of Apache Tika before 1.18. |
| CVE-2018-1335 | High | 2018-04-25 | Protected by Waratek | Exploited | 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. |