You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@zookeeper.apache.org by "Chris Nauroth (Jira)" <ji...@apache.org> on 2022/01/13 21:25:00 UTC

[jira] [Resolved] (ZOOKEEPER-4442) Support for log4j 2.17.1

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

Chris Nauroth resolved ZOOKEEPER-4442.
--------------------------------------
      Assignee: Chris Nauroth
    Resolution: Invalid

ZooKeeper is not impacted by the recent Log4J 2 CVEs, because it uses Log4J 1 instead of Log4J 2, so I'm going to close this issue.

The community is currently discussing next steps for Zookeeper's logging infrastructure in a few JIRA issues, pull requests and mail threads. I suggest watching those if you'd like to keep informed about progress.

https://issues.apache.org/jira/browse/ZOOKEEPER-2342
https://issues.apache.org/jira/browse/ZOOKEEPER-4427
https://github.com/apache/zookeeper/pull/1793
https://lists.apache.org/thread/1ktv03wvqtfg22d13c1yo1lgnjv6xpkt

> Support for log4j 2.17.1
> ------------------------
>
>                 Key: ZOOKEEPER-4442
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-4442
>             Project: ZooKeeper
>          Issue Type: Bug
>    Affects Versions: 3.6.3
>            Reporter: Abhisek Swain
>            Assignee: Chris Nauroth
>            Priority: Major
>             Fix For: 3.6.3
>
>
> Please update the dependency of log4j to 2.17.1 to avoid security vulnerabilities.



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