zookeeper-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Tubbs (Jira)" <j...@apache.org>
Subject [jira] [Commented] (ZOOKEEPER-4305) log4j CVE problem
Date Fri, 28 May 2021 15:33:00 GMT

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

Christopher Tubbs commented on ZOOKEEPER-4305:
----------------------------------------------

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)

Mime
View raw message