log4j2 vulnerability (CVE-2021-44228)

[#1]

Hello,

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?

Thanks,

Mor

[#2]

It is in deed an important question.

[#3]

Following - Cloudera please provide recommendations as this is really urgent.

[#4]

Please go through below apache docs, its might help 

https://logging.apache.org/log4j/2.x/manual/migration.html

[#5]

I upgraded log4j to 2.17 0, but the following error occurred when restarting hiveserver2:

[#6]

Hi All,

Is there any impact of CVE-2021-44228 - log4j Arbitrary RCE on CDH 5.x and 6.x??

Regards,

Hanu

[#7]

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.

[#8]

Hi Team,

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 ? 

Thanks

Srikanth

[#9]

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?

[#10]

Hi Thomas 

Could you please refer to below url , this statement came from apache, but not from Cloudera. 

https://logging.apache.org/log4j/2.x/security.html

Thanks

Srikanth

[#11]

Hi Srikanth,

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.

Regards,

Tom

[#12]

@ThomasHopewell Thank you for providing info, please let us know if you get any information on this issue . 

Thanks

Srikanth 

[#13]

Hi Team, 

There is a vulnerability reported for Log4J in in the below link:-

https://github.com/advisories/GHSA-jfh8-c2jp-5v3q

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

[#14]

Hive I believe is vulnerable and running 2.10.

[#15]

I'm also curious about hive, not sure how to remediate.

[#16]

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/

[#17]

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.

https://github.com/cloudera/cloudera-scripts-for-log4j

[#18]

Agreed. Glad to see anything being done, but an official message needs to be put out before I destroy production lol.

[#19]

All, please read the Cloudera blog article on this topic:

Cloudera Response to CVE-2021-4428

[#20]

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?

[#21]

@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?"