You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "ashok talari (Jira)" <ji...@apache.org> on 2022/01/03 14:22: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=17468014#comment-17468014 ]
ashok talari edited comment on KAFKA-9366 at 1/3/22, 2:21 PM:
--------------------------------------------------------------
Hi Dongjin Lee,
Could you please let us know if any tentative dates for official release for latest log4j build.
was (Author: JIRAUSER282960):
Hi Dongjin Lee,
Could you please let us know if any tentative dates for official release for latest log4j build.
> 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.2.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.20.1#820001)