[
https://issues.apache.org/jira/browse/HBASE-26557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17459023#comment-17459023
]
Duo Zhang commented on HBASE-26557:
-----------------------------------
Disable jndi is enough for HBase. For the problem described in 2.16.0, you need
to write something like %m{lookup}.
So it is not a blocker, but it is no harm to upgrade to 2.16.0. I've already
published the 3.0.0-alpha-2RC1, just need to send out the notice email. And for
hbase-operator-tools, I think we can include the upgrade of log4j2 if
[~gxcheng] has not done the release process yet.
Thanks.
> log4j2 has a critical RCE vulnerability
> ---------------------------------------
>
> Key: HBASE-26557
> URL: https://issues.apache.org/jira/browse/HBASE-26557
> Project: HBase
> Issue Type: Bug
> Components: logging, security
> Reporter: Yutong Xiao
> Assignee: Yutong Xiao
> Priority: Major
> Fix For: 3.0.0-alpha-2
>
>
> Impacted log4j version: Apache Log4j 2.x <= 2.14.1
> I found that our current log4j version at master is 2.14.1.
> Should upgrade the version to 2.15.0
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
