junrao commented on a change in pull request #388: URL: https://github.com/apache/kafka-site/pull/388#discussion_r768947897
########## File path: cve-list.html ########## @@ -9,6 +9,63 @@ <h1>Apache Kafka Security Vulnerabilities</h1> This page lists all security vulnerabilities fixed in released versions of Apache Kafka. +<h2><a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44228";>CVE-2021-44228</a> + Flaw in Apache Log4j logging library in versions from 2.0.0 and before 2.15.0</h2> + + <p>Some components in Apache Kafka use <code>Log4j-v1.2.17</code> there is no dependence on <code>Log4j v2.*</code></p> + + <p><a href="https://logging.apache.org/log4j/2.x/manual/lookups.html";>Lookups feature</a> was introduced in Log4j v2.x in order to allow specifying Log4j configuration parameters in arbitrary locations (even outside of the configuration files). Log4j v1.x does not offer the same functionality and thus is not vulnerable to <a href="https://access.redhat.com/security/cve/cve-2021-44228";>CVE-2021-44228</a>.</p> + <p>Users should NOT be impacted by this vulnerability</p> + + <table class="data-table"> + <tbody> + <tr> + <td>Versions affected</td> + <td>NA</td> + </tr> + <tr> + <td>Fixed versions</td> + <td>NA</td> + </tr> + <tr> + <td>Impact</td> + <td>NA</td> + </tr> + <tr> + <td>Issue announced</td> + <td>09 Dec 2021</td> + </tr> + </tbody> + </table> + +<h2><a href="https://access.redhat.com/security/cve/CVE-2021-4104";>CVE-2021-4104</a> + Flaw in Apache Log4j logging library in versions 1.x</h2> + + <p>Some components in Apache Kafka use <code>Log4j-v1.2.17</code></p> + + <p>Version 1.x of Log4J can be configured to use JMS Appender, which publishes log events to a JMS Topic. Log4j 1.x is vulnerable if the deployed application is configured to use JMSAppender.</p> + + <table class="data-table"> + <tbody> + <tr> + <td>Versions affected</td> + <td>All versions</td> + </tr> + <tr> + <td>Fixed versions</td> + <td>NA</td> Review comment: Since we don't have a fix yet, perhaps we could add the following. In the absence of a new log4j 1.x release, one can remove JMSAppender from the *log4j-1.2.17.jar* artifact. Commands are listed in the page <http://slf4j.org/log4shell.html>. We also recommend that configuration files be protected against write access as stated in <http://slf4j.org/log4shell.html>. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@kafka.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
