Apache Tika is vulnerable to entity expansions which can lead to a denial of service attack
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.
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2018-11796US | high7.5 | — | ||
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 par… | ||||
references
External citations — patches, advisories, analysis.
- http://www.securityfocus.com/bid/105585WEB
- https://access.redhat.com/errata/RHSA-2019:3892WEB
- https://github.com/advisories/GHSA-h8q5-g2cj-qr5hADVISORY
- https://github.com/apache/tikaPACKAGE
- https://lists.apache.org/thread.html/88de8350cda9b184888ec294c813c5bd8a2081de8fd3666f8904bc05@%3Cdev.tika.apache.org%3EWEB
- https://nvd.nist.gov/vuln/detail/CVE-2018-11796ADVISORY
- https://security.netapp.com/advisory/ntap-20190903-0002WEB
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan