You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tika.apache.org by "Tim Allison (Jira)" <ji...@apache.org> on 2022/01/05 12:10:00 UTC

[jira] [Resolved] (TIKA-3638) Log4J vulnerability mitigation by upgrading to latest

     [ https://issues.apache.org/jira/browse/TIKA-3638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tim Allison resolved TIKA-3638.
-------------------------------
    Fix Version/s: 2.2.2
                   1.28.1
       Resolution: Fixed

Thank you [~subhajitdas298] !

> Log4J vulnerability mitigation by upgrading to latest
> -----------------------------------------------------
>
>                 Key: TIKA-3638
>                 URL: https://issues.apache.org/jira/browse/TIKA-3638
>             Project: Tika
>          Issue Type: Bug
>    Affects Versions: 1.28, 2.2.1
>            Reporter: Subhajit Das
>            Priority: Major
>             Fix For: 2.2.2, 1.28.1
>
>
> Noticeable Vulnerability for log4j is still persistent in log4j 2.17.0.
> Upgrading to 2.17.1 (and any latest that may come up before release).
>  
> Ref:
> [https://mvnrepository.com/artifact/org.apache.logging.log4j/log4j-core/2.17.0]
> [https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44832]
> https://issues.apache.org/jira/browse/LOG4J2-3293



--
This message was sent by Atlassian Jira
(v8.20.1#820001)