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

Posted to jira@kafka.apache.org by "yale (Jira)" <ji...@apache.org> on 2021/09/01 12:12:00 UTC

[jira] [Comment Edited] (KAFKA-9366) Upgrade log4j to log4j2

    [ https://issues.apache.org/jira/browse/KAFKA-9366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17408133#comment-17408133 ] 

yale edited comment on KAFKA-9366 at 9/1/21, 12:11 PM:
-------------------------------------------------------

May I kindly ask about the plan to upgrade log4j to version 2.x? I see that mentioned PR is still open. Any plans for releasing it in 3.1? 
Thanks!


was (Author: yale):
May I kindly ask about the plan to upgrade log4j to version 2.x? I see that mentioned PR is still open. Any plans for releasing it in 3.1?

> Upgrade log4j to log4j2
> -----------------------
>
>                 Key: KAFKA-9366
>                 URL: https://issues.apache.org/jira/browse/KAFKA-9366
>             Project: Kafka
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 2.2.0, 2.1.1, 2.3.0, 2.4.0
>            Reporter: leibo
>            Assignee: Dongjin Lee
>            Priority: Critical
>              Labels: needs-kip
>             Fix For: 3.1.0
>
>
> h2. CVE-2019-17571 Detail
> Included in Log4j 1.2 is a SocketServer class that is vulnerable to deserialization of untrusted data which can be exploited to remotely execute arbitrary code when combined with a deserialization gadget when listening to untrusted network traffic for log data. This affects Log4j versions up to 1.2 up to 1.2.17.
>  
> [https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-17571]
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)