CLONE - Remove any reference to Log4Shell or Log4J Service in i21

Issue No: FRM-10083
Created 12/24/2021 12:07:37 AM
Type Bug
Priority Critical
Status Closed
Resolution Fixed
Fixed Version 19.1
Description There was a critical vulnerability found concerning Apache Open-Source code Log4j. We need to ensure we are not using this anywhere in i21 and remove it if we are. Several customers (Strauss, Dallmayr, etc.) are asking about this.   Here are more details from SentinelOne.   {color:#3f4259}On Friday, December 9, 2021, a new vulnerability named “Log4Shell” emerged allowing adversaries to execute code on any server running the Java logging library Apache log4j. This vulnerability impacts websites, applications, software, and services including Microsoft, Apple, Google, AWS, and more. {color}     *{color:#3f4259}Your SentinelOne Singularity XDR platform protects against Log4Shell exploitation attempts across operating systems.{color}* {color:#3f4259} Watch our [demos|https://go2.sentinelone.com/MzI3LU1OTS0wODcAAAGBUY-wZlzR3QIMjMRRSFE_rKFOWnWZJa35L0xRMD_4t_i3-6R7kWs8RNRn0Azyb5ttdKxd7dk=] to see how SentinelOne protects against a public and weaponized POC. Guidance to stay protected:{color}   # {color:#666666}We recommend that SentinelOne is deployed across your environment for protection and visibility; we also recommend you patch vulnerable assets.{color} # {color:#666666}Stay up-to-date by reading our blog, “ *[CVE-2021-44228: Staying Secure – Apache Log4j Vulnerability|https://go2.sentinelone.com/MzI3LU1OTS0wODcAAAGBUY-wZlzR3QIMjMRRSFE_rKFOWnWZJa35L0xRMD_4t_i3-6R7kWs8RNRn0Azyb5ttdKxd7dk=] .* ” {color} # {color:#666666} *SentinelOne Vigilance MDR customers* - your environment is constantly being monitored for evidence of exploit attempts. Your Vigilance team will contact you for risk mitigation. {color}   {color:#3f4259}As your security partner, SentinelOne is here to keep you protected and informed.{color}     {color:#3f4259}Happy holidays,{color} {color:#3f4259}SentinelOne{color}       *{color:#3f4259}Steps:{color}*   {color:#3f4259}1. Go to Application Path > bin folder{color}   *{color:#3f4259}Issue:{color}*   {color:#3f4259}The following dlls displayed:{color}   * {color:#3f4259}log4net.dll{color} * {color:#3f4259}ActiveDatabaseSoftware.ActiveQueryBuilder.dll{color} * {color:#3f4259}ActiveDatabaseSoftware.ActiveQueryBuilder.Web.Control.dll{color} * {color:#3f4259}ActiveDatabaseSoftware.ActiveQueryBuilder.Web.Server.dll{color} * {color:#3f4259}ActiveDatabaseSoftware.MSSQLCEMetadataProvider.dll{color} * {color:#3f4259}ActiveDatabaseSoftware.MSSQLMetadataProvider.dll{color} * {color:#3f4259}ActiveDatabaseSoftware.MySQLMetadataProvider.dll{color} * {color:#3f4259}ActiveDatabaseSoftware.ODBCMetadataProvider.dll{color} * {color:#3f4259}ActiveDatabaseSoftware.ODBCMetadataProvider.dll{color} * {color:#3f4259}ActiveDatabaseSoftware.OLEDBMetadataProvider.dll{color} * {color:#3f4259}ActiveDatabaseSoftware.OracleMetadataProvider.dll{color}   *{color:#3f4259}Accepted:{color}*   {color:#3f4259}The following dlls should be removed in bin folder:{color}   * {color:#3f4259}log4net.dll{color} * {color:#3f4259}ActiveDatabaseSoftware.ActiveQueryBuilder.dll{color} * {color:#3f4259}ActiveDatabaseSoftware.ActiveQueryBuilder.Web.Control.dll{color} * {color:#3f4259}ActiveDatabaseSoftware.ActiveQueryBuilder.Web.Server.dll{color} * {color:#3f4259}ActiveDatabaseSoftware.MSSQLCEMetadataProvider.dll{color} * {color:#3f4259}ActiveDatabaseSoftware.MSSQLMetadataProvider.dll{color} * {color:#3f4259}ActiveDatabaseSoftware.MySQLMetadataProvider.dll{color} * {color:#3f4259}ActiveDatabaseSoftware.ODBCMetadataProvider.dll{color} * {color:#3f4259}ActiveDatabaseSoftware.ODBCMetadataProvider.dll{color} * {color:#3f4259}ActiveDatabaseSoftware.OLEDBMetadataProvider.dll{color} * {color:#3f4259}ActiveDatabaseSoftware.OracleMetadataProvider.dll{color}