[
https://issues.apache.org/jira/browse/KAFKA-13535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17458213#comment-17458213
]
Luke Chen commented on KAFKA-13535:
-----------------------------------
[~akansh] , I think if users don't add jms appender config to log4j
configuration file, with the *TopicBindingName* or
*TopicConnectionFactoryBindingName* setting to bad names, it's fine. I would
suggest Kafka team has an official announcement for this vulnerability. Thanks.
> Workaround for mitigating CVE-2021-44228 Kafka
> -----------------------------------------------
>
> Key: KAFKA-13535
> URL: https://issues.apache.org/jira/browse/KAFKA-13535
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 2.8.1
> Reporter: Akansh Shandilya
> Priority: Major
>
> Kafka v2.8.1 uses log4j v1.x . Please review following information :
>
> Is Kafka v2.8.1 impacted by CVE-2021-44228?
> If yes, is there any workaround/recommendation available for Kafka v2.8.1 to
> mitigate CVE-2021-44228
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
