[
https://issues.apache.org/jira/browse/ZOOKEEPER-4423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17458254#comment-17458254
]
Sourabh Sarvotham Parkala commented on ZOOKEEPER-4423:
------------------------------------------------------
Hello Team,
The urgency to get this issue sorted out seems to be really overwhelming.
I understand the discussion is still ongoing to confirm if this CVE affects
log4j 1.x or not.
But since log4j 1.x has been EOL for 6 years now, it does make sense to migrate
to log4j2 as soon as possible.
Please let me know your thoughts regarding this.
Thanks
Sourabh
> Upgrade Log4j to 2.15.0 - CVE-2021-44228
> ----------------------------------------
>
> Key: ZOOKEEPER-4423
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-4423
> Project: ZooKeeper
> Issue Type: Task
> Affects Versions: 3.6.0, 3.6.3, 3.7.0, 3.6.1, 3.6.2, 3.6.4
> Reporter: Sai Kiran Vudutala
> Priority: Major
>
> Log4j has an RCE vulnerability, see
> [https://www.lunasec.io/docs/blog/log4j-zero-day/]
> References.
> [https://github.com/advisories/GHSA-jfh8-c2jp-5v3q]
> [https://github.com/apache/logging-log4j2/pull/608#issuecomment-990494126]
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
