[jira] [Comment Edited] (ZOOKEEPER-4305) log4j CVE problem

["Christopher Tubbs (Jira)" <ji...@apache.org>]

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

Christopher Tubbs edited comment on ZOOKEEPER-4305 at 5/28/21, 3:32 PM:
------------------------------------------------------------------------

Hi [~neal zhao]; thanks for opening this issue. This issue already been addressed in several prior JIRA tickets. I have closed this and marked it as a duplicate. In future, please search JIRA for any existing ticket prior to opening a new one. The search for "zookeeper CVE-2019-17571" and "zookeeper socketserver" both show prior tickets for this issue with answers to your questions.


was (Author: ctubbsii):
Hi [~neal zhao]; thanks for opening this issue. This issue already been addressed in several prior JIRA tickets. I have closed this and marked it as a duplicate. In future, please search JIRA for any existing ticket prior to opening a new one. The search for "zookeeper CVE-2019-17571" and "zookeeper socketserver" both show prior tickets for this issue.

> log4j CVE problem
> -----------------
>
>                 Key: ZOOKEEPER-4305
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-4305
>             Project: ZooKeeper
>          Issue Type: Bug
>          Components: security
>    Affects Versions: 3.6.2, 3.7
>            Reporter: zhaozhengbin
>            Priority: Critical
>
> 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.



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