Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1639090 - (CVE-2018-11796) CVE-2018-11796 tika: Incomplete fix allows for XML entity expansion resulting in denial of service
CVE-2018-11796 tika: Incomplete fix allows for XML entity expansion resulting...
Status: NEW
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
high Severity high
: ---
: ---
Assigned To: Red Hat Product Security
impact=important,public=20181010,repo...
: Security
Depends On: 1639092
Blocks: 1639093
  Show dependency treegraph
 
Reported: 2018-10-15 00:21 EDT by Sam Fowler
Modified: 2018-10-15 00:24 EDT (History)
40 users (show)

See Also:
Fixed In Version: tika 1.19.1
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Sam Fowler 2018-10-15 00:21:31 EDT
Apache Tika 1.19 included an incomplete fix for CVE-2018-11761 which 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 1.19 is therefore still vulnerable to entity expansions which can lead to a denial of service attack.


External Reference:

https://lists.apache.org/thread.html/88de8350cda9b184888ec294c813c5bd8a2081de8fd3666f8904bc05@%3Cdev.tika.apache.org%3E


Upstream Issue:

https://issues.apache.org/jira/projects/TIKA/issues/TIKA-2727


Upstream Patch:

https://github.com/apache/tika/commit/86d4ba1e
Comment 1 Sam Fowler 2018-10-15 00:22:16 EDT
Created tika tracking bugs for this issue:

Affects: fedora-all [bug 1639092]

Note You need to log in before you can comment on or make changes to this bug.