I wanted to ask if there's a page / instructions / info regarding the recent log4j2 vulnerability (https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44228) and how it can affect Cloudera CDH setups? If it does affect, what are the recommended mitigations on it?
Created 12-12-2021 01:41 AM
It is in deed an important question.
Created 12-12-2021 01:33 PM
Following - Cloudera please provide recommendations as this is really urgent.
Created 12-12-2021 07:26 PM
Please go through below apache docs, its might help
Created 12-24-2021 12:05 AM
I upgraded log4j to 2.17 0, but the following error occurred when restarting hiveserver2:
Created 12-12-2021 11:30 PM
Is there any impact of CVE-2021-44228 - log4j Arbitrary RCE on CDH 5.x and 6.x??
Created 12-13-2021 05:59 AM
Cloudera platform security teams are actively assessing the impact to our on-premises and cloud products and will provide an impact analysis update to customers as soon as possible.
Created 12-13-2021 01:41 AM
Currenlty in our organization we are using Cloudera 6.3.1 express edition, recently our company security team came up with log4j CVE-2021-44228 vulnerable, Could you please suggest due to this any problem for cloudera ?
Created 12-13-2021 02:04 AM
I second this question. I currently administer a CDH 5.16 cluster that we're in the process of upgrading to CDP 7.x. Is there a statement from cloudera about the extent of the vulnerablility in their products and how we can go about patching it?
Created 12-13-2021 02:19 AM
Could you please refer to below url , this statement came from apache, but not from Cloudera.
Created 12-13-2021 05:54 AM
Thanks for that, it's a helpful link.
It would still be great to get something offical from Cloudera. I've emailed our rep with them to see if he has any info. If he gets back to me, I'll drop anything relevant back into this thread.
Created 12-14-2021 12:37 AM
@ThomasHopewell Thank you for providing info, please let us know if you get any information on this issue .
Created on 12-13-2021 02:24 AM - edited 12-13-2021 02:58 AM
There is a vulnerability reported for Log4J in in the below link:-
As per our knowledge, NIFI uses LOGback which is a successor of Log4J, so we should not be having any issues/vulnerabilities with NIFI. But, we wanted to be sure of the same. Please share if in case anyone has any thoughts for NIFI over this.
We are using NIFI 1.8 currently in our organization which uses Logback 1.1.3
Created 12-13-2021 08:26 AM
Hive I believe is vulnerable and running 2.10.
Created 12-13-2021 11:00 AM
I'm also curious about hive, not sure how to remediate.
Created 12-13-2021 11:04 AM
Obviously, the best solution would be to replace all jars with the latest Log4j2 jars, but the way Cloudera does things now it might break things. In the long term, better to wait for them to make a statement.
Here's a link that may help, look under workarounds: https://msrc-blog.microsoft.com/2021/12/11/microsofts-response-to-cve-2021-44228-apache-log4j2/
Created 12-13-2021 11:09 AM
I noticed this new repo on Cloudera's GitHub but have not seen any official communication about it on Cloudera's site, from our account team, or via the proactive support channels - that makes me leery about using it in our environment.
Created 12-13-2021 11:15 AM
Agreed. Glad to see anything being done, but an official message needs to be put out before I destroy production lol.
Created 12-13-2021 11:58 AM
All, please read the Cloudera blog article on this topic:
Cloudera Response to CVE-2021-4428
Created 12-13-2021 01:47 PM
The TSB is not available unless you have a Knowledge Base subscription. Given the severity of the problem, will this information be made available to the public?
Created on 12-13-2021 01:55 PM - last edited on 12-13-2021 10:46 PM by VidyaSargur
@Eric_B Yes. There is a link for non-customers of Cloudera in the blog article linked above. It's at the end of the paragraph beginning "What Cloudera products and versions are affected?"