[
https://issues.apache.org/jira/browse/KAFKA-13535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17458016#comment-17458016
]
Akansh Shandilya commented on KAFKA-13535:
------------------------------------------
Hi [~showuon],
But as long as you're using Kafka, and not setting the log4j jms configuration:
*TopicBindingName* or *TopicConnectionFactoryBindingName* to something that
JNDI can handle, ex: "ldap://host:port/a";
>> Thanks a lot, for keep sharing of latest update. Do we have any recommended
>> steps to validate something, i.e. log4j configuration filename etc.
> 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)
