Closed bikashg closed 1 year ago
After the Tika team releases CVE-2021-44228 fixed version. Tika 2.1.0 is the first Tika release to use log4j2 which most likely within the identified Log4J2 versions that have the CVE-2021-44228 vulnerability.
Apache Tika 2.2.1 has implemented Log4J2 2.17.0, which has addressed all but the most recent CVE-2021-44832 that requires an attacker to have access to the actual configuration file. It appears that Tika is in no hurry to release a new version with Log4J2 2.17.1. So, the question is: Will tika-python be waiting until this happens even with the vulnerabilities that Apache Tika 1.24.1 has?
Tika 2.3.0 addressed log4j 2.17.1 , so that seems to satisfy the remaining issue here.
Moreover, we're now at Tika 2.4.1 AND 1.x will stop receiving updates in 3 weeks (Sept 30,2022). So, we really need to make this project compatible with the latest versions.
@chrismattmann thanks for all you've done, but could you please give us some guidance as to whether this project is completely abandoned now? Should those who are using it make other plans - be it forking it or something else?
@nickchomey @bikashg Our requests have been heard and it's now an active WIP (see #377).
thanks, sorry for the delays on updates. I will spend some time over the winter holidays here getting this merged.
OK not in this release (which is going to be 1.24.2) but I have 2 PRs I will look at for 2.6.x release which I will make next week. Thanks. This 1.24.2 release will include all the updates the past 2 years that haven't been released.
Hi @chrismattmann ,
Fantastic library! I was wondering if you have near plans/roadmap to make it compatible with Apache Tika version 2.1.0
I used the
tika-server-standard-2.1.0.jar
file fromhttps://tika.apache.org/download.html
to run locally on my machine but get the following error: