You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@kafka.apache.org by "Luke Chen (Jira)" <ji...@apache.org> on 2021/12/15 06:04:00 UTC

[jira] [Commented] (KAFKA-13545) Workaround for mitigating CVE-2021-4104 Kafka

    [ https://issues.apache.org/jira/browse/KAFKA-13545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17459667#comment-17459667 ] 

Luke Chen commented on KAFKA-13545:
-----------------------------------

[~akansh] , please check the official statement for this CVE here: [https://kafka.apache.org/cve-list]  for the mitigation ways. Thanks.

> Workaround for mitigating CVE-2021-4104 Kafka 
> ----------------------------------------------
>
>                 Key: KAFKA-13545
>                 URL: https://issues.apache.org/jira/browse/KAFKA-13545
>             Project: Kafka
>          Issue Type: Bug
>    Affects Versions: 2.8.1
>            Reporter: Akansh Shandilya
>            Priority: Major
>
> A new vulnerability is published today :
> https://nvd.nist.gov/vuln/detail/CVE-2021-4104
>  
> Kafka v2.8.1 uses log4j v1.x . Please review following information :
> Is Kafka v2.8.1 impacted by  CVE-2021-4104?
> If yes, is there any workaround/recommendation available for Kafka  v2.8.1 to mitigate CVE-2021-4104



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