Notice: On December 14, 2021 the Apache Software Foundation notified the community that their initial guidance for CVE-2021-44228 workarounds was not sufficient. We believe the instructions in this article to be an effective mitigation for CVE-2021-44228, but in the best interest of our customers we must assume this workaround may not adequately address all attack vectors. We expect to fully address CVE-2021-44228, CVE-2021-45046 and CVE-2021-45105 by updating log4j to version 2.17 in forthcoming releases of “VMware Smart Assurance SAM [Service Assurance Manager]”, as outlined by our software support policies. VMSA-2021-0028 will be updated when these releases are available. In the interim, we have updated this Knowledge Base article with revised guidance to remove all JndiLookup classes per Apache Software Foundation guidance.
Please subscribe to this article to be informed when updates are published.
The workaround described in this article is meant to be a temporary solution only. Upgrades documented in the aforementioned advisory should be applied to remediate CVE-2021-44228 when available.
• Smarts ElasticSearch
VMware Smart Assurance Service Assurance Manager(SAM) 10.1.0.16
Refer: VMware Smart Assurance 10.1.0.16 Patch Release notes for more details
VMware Smart Assurance Service Assurance Manager(SAM) 10.1.2.16
Refer: VMware Smart Assurance 10.1.2.16 Patch Release notes for more details
VMware Smart Assurance Service Assurance Manager(SAM) 10.1.5.5
Refer: VMware Smart Assurance 10.1.5.5 Patch Release notes for more details
• CVE-2021-44228 - Log4j2 JNDI features do not protect against attacker-controlled LDAP and other JNDI related endpoints
• CVE-2021-45046 - Log4j2 Thread Context Lookup Pattern vulnerable to remote code execution in certain non-default configurations
• CVE-2021-45105 - Avoid the uncontrolled recursion from self-referential Context lookups.
• CVE-2021-4104 - JMSAppender in Log4j 1.x is vulnerable to deserialization of untrusted data. This allows a remote attacker to execute code on the server if the deployed application is configured to use JMSAppender and to the attacker's JNDI LDAP endpoint.
Regarding the CVE-2021-44832 which reported following vulnerabilities:
• Removal of LDAP protocol while making JNDI connections.
Note that VMware Smart Assurance SAM (Service Assurance Manager), does not make any JNDI connection as the complete JNDI lookup class has been removed in 2.17.
Hence the same remain unexploited with no exposure on Smarts.
3. Execute the below command to remove the class JndiLookup.class from the “log4j-core-2.11.1.jar” file.
zip -q -d log4j-core-*.jar org/apache/logging/log4j/core/lookup/JndiLookup.class
4. Restart elastic search service.
Change Log: