<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>question Cloudera response to CVE-2021-4104 in Community Announcements</title>
    <link>https://community.cloudera.com/t5/Community-Announcements/Cloudera-response-to-CVE-2021-4104/m-p/332287#M68</link>
    <description>&lt;P&gt;&lt;SPAN style="font-weight: 400;"&gt;Cloudera is aware of &lt;/SPAN&gt;&lt;A href="https://nvd.nist.gov/vuln/detail/CVE-2021-4104" target="_blank" rel="noopener"&gt;&lt;SPAN style="font-weight: 400;"&gt;CVE-2021-4104&lt;/SPAN&gt;&lt;/A&gt;&lt;SPAN style="font-weight: 400;"&gt;, which affects the Apache Log4j 1.x JMSAppender. This flaw only affects software that is explicitly configured to use the JMSAppender, which is not the default, or when the attacker has write access to the Log4j configuration for adding JMSAppender. Cloudera does not use JMSAppender in its products and it is not used by default in log4j properties. Cloudera customers do not need to take any action to address CVE-2021-4104. If you have further questions, please contact Cloudera Support through our &lt;/SPAN&gt;&lt;A href="https://my.cloudera.com/" target="_blank" rel="noopener"&gt;&lt;SPAN style="font-weight: 400;"&gt;My Cloudera&lt;/SPAN&gt;&lt;/A&gt;&lt;SPAN style="font-weight: 400;"&gt; Support portal.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="font-weight: 400;"&gt;Because Cloudera Manager and Ambari allow authenticated users with privileged access to modify cluster configuration to insert custom logging configuration, customers are advised to review the logging configuration for their clusters to ensure that they do not contain references to the JMSAppender. To find these settings, look for the following based on the cluster management tool in use:&lt;/SPAN&gt;&lt;/P&gt;
&lt;UL&gt;
&lt;LI style="font-weight: 400;" aria-level="1"&gt;&lt;SPAN style="font-weight: 400;"&gt;Cloudera Manager: "{SERVICE_NAME} Logging Advanced Configuration Snippet (Safety Valve)"&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI style="font-weight: 400;" aria-level="1"&gt;&lt;SPAN style="font-weight: 400;"&gt;Ambari: “Advanced{SERVICE_NAME}-log4j”&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;</description>
    <pubDate>Wed, 15 Dec 2021 22:44:48 GMT</pubDate>
    <dc:creator>cjervis</dc:creator>
    <dc:date>2021-12-15T22:44:48Z</dc:date>
    <item>
      <title>Cloudera response to CVE-2021-4104</title>
      <link>https://community.cloudera.com/t5/Community-Announcements/Cloudera-response-to-CVE-2021-4104/m-p/332287#M68</link>
      <description>&lt;P&gt;&lt;SPAN style="font-weight: 400;"&gt;Cloudera is aware of &lt;/SPAN&gt;&lt;A href="https://nvd.nist.gov/vuln/detail/CVE-2021-4104" target="_blank" rel="noopener"&gt;&lt;SPAN style="font-weight: 400;"&gt;CVE-2021-4104&lt;/SPAN&gt;&lt;/A&gt;&lt;SPAN style="font-weight: 400;"&gt;, which affects the Apache Log4j 1.x JMSAppender. This flaw only affects software that is explicitly configured to use the JMSAppender, which is not the default, or when the attacker has write access to the Log4j configuration for adding JMSAppender. Cloudera does not use JMSAppender in its products and it is not used by default in log4j properties. Cloudera customers do not need to take any action to address CVE-2021-4104. If you have further questions, please contact Cloudera Support through our &lt;/SPAN&gt;&lt;A href="https://my.cloudera.com/" target="_blank" rel="noopener"&gt;&lt;SPAN style="font-weight: 400;"&gt;My Cloudera&lt;/SPAN&gt;&lt;/A&gt;&lt;SPAN style="font-weight: 400;"&gt; Support portal.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="font-weight: 400;"&gt;Because Cloudera Manager and Ambari allow authenticated users with privileged access to modify cluster configuration to insert custom logging configuration, customers are advised to review the logging configuration for their clusters to ensure that they do not contain references to the JMSAppender. To find these settings, look for the following based on the cluster management tool in use:&lt;/SPAN&gt;&lt;/P&gt;
&lt;UL&gt;
&lt;LI style="font-weight: 400;" aria-level="1"&gt;&lt;SPAN style="font-weight: 400;"&gt;Cloudera Manager: "{SERVICE_NAME} Logging Advanced Configuration Snippet (Safety Valve)"&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI style="font-weight: 400;" aria-level="1"&gt;&lt;SPAN style="font-weight: 400;"&gt;Ambari: “Advanced{SERVICE_NAME}-log4j”&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;</description>
      <pubDate>Wed, 15 Dec 2021 22:44:48 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Community-Announcements/Cloudera-response-to-CVE-2021-4104/m-p/332287#M68</guid>
      <dc:creator>cjervis</dc:creator>
      <dc:date>2021-12-15T22:44:48Z</dc:date>
    </item>
  </channel>
</rss>

