[
https://issues.apache.org/jira/browse/TIKA-3488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17388047#comment-17388047
]
Tim Allison commented on TIKA-3488:
-----------------------------------
We appear to use jdom2 in two parsers: rome (FeedParser) and ucar. It looks
like we can mitigate this in rome by loading the jdom2 document ourselves[1].
I don't see that there's anything we can do in ucar, but if anyone has any
recs, let me know.
If you're using tika 2.x and don't need the scientific parsers, then you'll be
all set with the tika-parsers-standard. This was one of the reasons for
modularization! :D
[1] https://github.com/hunterhacker/jdom/issues/189#issuecomment-867933052
> Security issue XXE in TIKA due to JDOM
> --------------------------------------
>
> Key: TIKA-3488
> URL: https://issues.apache.org/jira/browse/TIKA-3488
> Project: Tika
> Issue Type: Bug
> Components: tika-server
> Affects Versions: 1.25
> Reporter: Arvind Jagtap
> Priority: Major
>
> Apache TIKA 1.35 is vulnerable due to dependency on JDOM 2.0.6. Black Duck
> Hub has reported this vulnerability CVE-2021-33813 with more detail on the
> following page.
> [https://nvd.nist.gov/vuln/detail/CVE-2021-33813#range-6782705]
> Although the following issue is entered, it is not yet fixed and there is no
> timeline given.
> https://github.com/hunterhacker/jdom/issues/189
> There are some workaround discussed on this issue. Can this be fixed in TIKA
> in the meanwhile?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
