Support Announcements

Cloudera is aware of CVE-2021-4104, 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 My Cloudera Support portal.

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:

• Cloudera Manager: "{SERVICE_NAME} Logging Advanced Configuration Snippet (Safety Valve)"
• Ambari: “Advanced{SERVICE_NAME}-log4j”

Prepare for the End of Support (EoS) of Cloudera Enterprise 6.x and HDP 3.1 by leveraging predictive validations to avoid known upgrade issues.

Cloudera Support's cluster validations program proactively identifies known problem signatures contained in customers' diagnostic data with the goal of increasing cluster health, performance, and overall stability.

10 seconds determines the CDP readiness of your cluster!

Responses to common questions about the MyCloudera Support Case Experience. 

Portal will be down for maintenance over the weekend

Don’t miss out! Learn how to use the upgraded MyCloudera Portal now

Case Creation and Case Management is about to get a lot easier. 

Coming in November we will upgrade the Cloudera support portal to provide a better customer experience.

Sneak peek: a new Cloudera Support Experience launches this November!