.png)
CVE-2021-44228
Impacted products:
| Affected Products | Version Details | Components | Log4j Version | Mitigation |
| PKWARE Appliance (Legacy) | Ubuntu 16 based appliance | Elasticsearch | 2.11.1 | Upgrade 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 Appliance | Ubuntu 20 based appliance | Elasticsearch | 2.11.1 | Log4j 2.17.1 included in January 2022 security patch 2022.01.1 |
| Elasticsearch 5.6 (3rd party application) | Elasticsearch 5.6 | Elasticsearch | 2.9.1 | Upgrade 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.9 | Elasticsearch | 2.11.1 | PKWARE will provide upgrade to Elasticsearch 7.16.2 |
| PKWARE Smarcrypt Client | Smartcrypt 15.5 - Present | Smartcrypt.jar | 1.X | Upgrade to supported redaction processing |
| PKWARE Smarcrypt Client | Smartcrypt 16.40 - 16.60 | Redaction.jar | 2.13.1 | Upgrade to supported redaction processing |
| PKWARE Smarcrypt / PK Protect Client | Smartcrypt 16.7 - Present | Unpacker.jar | 2.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 Protect | All versions | Various | Various | Upgrade to v8.4 - updated with log4j 2.17.1 - released January 2022 |
| PKWARE / Dataguise DgSecure / PK Protect | All versions | DgWalkerAgent.jar DgLogReader.jar | Various | Upgrade 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.