Impacted products:

Affected ProductsVersion DetailsComponentsLog4j VersionMitigation
PKWARE Appliance (Legacy)Ubuntu 16 based applianceElasticsearch2.11.1Upgrade to new PKWARE appliance or follow ES mitigation (https://discuss.elastic.co/t/apache-log4j2-remote-code-execution-rce-vulnerability-cve-2021-44228-esa-2021-31/291476
PKWARE ApplianceUbuntu 20 based applianceElasticsearch2.11.1Log4j 2.17.1 included in January 2022 security patch 2022.01.1
Elasticsearch 5.6 (3rd party application)Elasticsearch 5.6Elasticsearch2.9.1Upgrade to new supported Elasticsearch or follow ES mitigation (https://discuss.elastic.co/t/apache-log4j2-remote-code-execution-rce-vulnerability-cve-2021-44228-esa-2021-31/291476)
Elasticsearch (3rd party application)Elasticsearch 7.9Elasticsearch2.11.1

PKWARE will provide upgrade to Elasticsearch 7.16.2
https://pkware.cachefly.net/products/smartcrypt/tools/elasticsearch-7.16.2.msi

PKWARE Smarcrypt ClientSmartcrypt 15.5 - PresentSmartcrypt.jar1.XUpgrade to supported redaction processing
PKWARE Smarcrypt ClientSmartcrypt 16.40 - 16.60Redaction.jar2.13.1Upgrade to supported redaction processing
PKWARE Smarcrypt / PK Protect  ClientSmartcrypt 16.7 - PresentUnpacker.jar2.13.1
2.14.1
16.70.X - Manually install new unpacker.jar ontop of existing unpacker.jar
16.80.0014 - Unpacker.jar updated with log4j 2.17.1
16.95.0015 - Unpacker.jar updated with log4j 2.17.1
17.00.0016  - Unpacker.jar updated with log4j 2.17.1
17.10.0017 - Unpacker.jar updated with log4j 2.17.1
PKWARE / Dataguise DgSecure / PK ProtectAll versionsVariousVariousUpgrade to v8.4 - updated with log4j 2.17.1 - released January 2022
PKWARE / Dataguise DgSecure / PK ProtectAll versions

DgWalkerAgent.jar

DgLogReader.jar

VariousUpgrade to v8.4 - updated with log4j 2.17.1 - released January 2022

Details:

Apache Log4j2 <=2.14.1 JNDI features used in configuration, log messages, and parameters do not protect against attacker controlled LDAP and other JNDI related endpoints. An attacker who can control log messages or log message parameters can execute arbitrary code loaded from LDAP servers when message lookup substitution is enabled. From log4j 2.15.0, this behavior has been disabled by default. In previous releases (>2.10) this behavior can be mitigated by setting system property "LOG4J_FORMAT_MSG_NO_LOOKUPS" to “true” or it can be mitigated in prior releases (<2.10) by removing the JndiLookup class from the classpath (example: zip -q -d log4j-core-*.jar org/apache/logging/log4j/core/lookup/JndiLookup.class). The log4j 2.17.1 release resolves all known vulnerabilities in log4j, and all PKWARE products now include this version.