How to patch the SearchBlox Server to fix the Log4j 2 exploit (CVE-2021-44228) vulnerability? – SearchBlox Help Center

Here is the fix to address the vulnerability - SearchBlox 10.0

1. Stop SearchBlox Service

2. Remove the two files log4j-core-2.1x.y.jar, log4j-api-2.1x.y.jar from the following folder path within SearchBlox and Elasticsearch paths.

Windows

\SearchBloxServer\webapps\ROOT\WEB-INF\lib\

\SearchBloxServer\elasticsearch\lib\

Linux

/opt/searchblox/webapps/ROOT/WEB-INF/lib/

/opt/searchblox/elasticsearch/lib/

3. Copy the 2 new files you have extracted from the zip file to the SearchBlox and Elasticsearch paths.

4. Start SearchBlox service

Here is the fix to address the vulnerability - SearchBlox 9.x

1. Stop SearchBlox and Elasticsearch Service

2. Remove the two files log4j-core-2.1x.y.jar, log4j-api-2.1x.y.jar from the following folder path within SearchBlox and Elasticsearch paths.

Windows

\SearchBloxServer\webapps\searchblox\WEB-INF\lib\

\SearchBloxServer\elasticsearch\lib\

Linux

/opt/searchblox/webapps/searchblox/WEB-INF/lib/

/opt/searchblox/elasticsearch/lib/

3. Copy the 2 new files you have extracted from the zip file to the SearchBlox and Elasticsearch paths.

4. Start Elasticsearch and SearchBlox service

Here is the fix to address the vulnerability - SearchBlox 8.x

Please note that this log4j-core-2.8.jar file does not contain the JNDI lookup class which is the root cause of the vulnerability.

1. Stop SearchBlox service

2. Remove the current file log4j-core-2.8.jar from the WEB-INF/lib folder within SearchBlox.

Windows

\SearchBloxServer\webapps\searchblox\WEB-INF\lib\

Linux

/opt/searchblox/webapps/searchblox/WEB-INF/lib/

3. Copy the new log4j-core-2.8.jar you have downloaded from the link above to the same path

4. Start SearchBlox service

If you prefer not to use log4j 2.8 then please upgrade to SearchBlox 10.0

Related articles