Hi David, recently we have received about Apache Log4j2 Remote Code Execution (RCE) Vulnerability.
I am using FS Crawler 2.4 version along with ELK 6.8.14, we planned to do remediation plan for log4j in ELK. We would like to know, if we need to what steps we need to do remediation plan for log4j in FS Crawler.
Please share your suggestions.
Thanks in advance,
Joseph
Actually FS Crawler 2.4 is using Log4J 2.8.1 version.
As per our security team says 'JAVA_OPTS="$JAVA_OPTS
-Dlog4j2.formatMsgNoLookups=true"' not valid/applicable for the Log4J versions with version less than V 2.10.
For releases from 2.0-beta9 to 2.10.0, the mitigation is to remove the JndiLookup class from the classpath: zip -q -d log4j-core-*.jar org/apache/logging/log4j/core/lookup/JndiLookup.class
Hi David,
Now, we have LOG4J 2.17.
Could You please suggest, if we need to use this version into FS Crawler 2.4 Version, what action we need to take in our end.
Hi David, Could You please share your comments..
One more query like while installing FS Crawler 2.9, Can we update the log4j--2.17.2 in the lib folder as we get latest of log4j?.
Currently, log4j--2.17.1 bundled with FS Crawler 2.9.
Thanks,
Joseph
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.