CluedIn Security - Log4j2 CVE-2021-44228security
On December 9th 2021 a high severity vulnerability was disclosed in the Apache Log4j2 library for all versions between 2.0-beta9 and 2.14.1. This library is used by a significant amount of Java based applications and services.
At CluedIn, we build .NET and Node.js services that are not impacted by the vulnerability. However, we do utilise some third-party services that are Java based.
This announcement details the usage of those services and their exposure to CVE-2021-44228.
After the intial wave of fixes an additonal issue was discovered (CVE-2021-45-46) which highlighted that in some cases the proposed fixes for CVE-2021-44228 were insufficient.
In all cases, no actions are required for CluedIn services. Notably Elasticsearch may have false positives, however Elastic reccomends the same changes as for the orginal CVE.
Therefore, there are no additonal requirments for fixes with CluedIn.
All versions of CluedIn use the 3.5.x (currently 3.5.29) version of the community edition of Neo4j or an earlier version.
As identified in the Neo4j repository, versions prior to 4.2 used a custom logging framework and are not affected by the vulnerability.
Additionally – Neo4j is not exposed to the public internet so user crafted requests that could expose the vulnerability cannot be targeted to the service.
No action is required for the current nor any previous version of CluedIn.
CluedIn 3.1.0-3.2.5 uses the 7.8.0 version of Elasticsearch. As identified by Elastic, Elasticsearch version 7.8+ running on JDK9+ are not susceptible.
CluedIn 3.0.0 uses 7.6.2 and will require setting a JVM option to prevent exposure.
Additionally – Elasticsearch is not exposed to the public internet so user crafted requests that could expose the vulnerability cannot be targeted to the service.
CluedIn Version 3.0.0
• In your
values.yml set the following
elasticsearch: esJavaOpts: “-Dlog4j2.formatMsgNoLookups=true”
• Perform a
helm upgrade with the new
No action is required for version 3.1+ of CluedIn.
CluedIn 3.2.2-3.2.5 uses the 3.4.1 version of OpenRefine. OpenRefine uses version 1.x of Log4j which does not contain the features which enable exposure to the vulnerability.
All earlier versions of CluedIn use the 3.1 version of OpenRefine. Again, version 1.x of Log4j is used, which does not contain the features which enable exposure to the vulnerability.
No action is required.