XPLG Products are not affected by the Apache Log4j vulnerability exploit, Log4Shell CVE-2021-44228 / CVE-2021-45046
*Updated Dec 19, 2021
No action should be taken with any of XPLG products.
The Log4J vulnerability exploits (Log4Shell exploit CVE-2021-44228, CVE-2021-45046) recently published do not affect the XPLG product suite.
Please be advised:
- Log4J Zero day was announced on Fri, Dec 10, as the highest (10.0 CVSS) critical Log4j vulnerability was discovered. The Log4Shell vulnerability was exploited by attackers worldwide, allowing malicious strings to be logged.
- Apache Log4j is an open-source Java package that allows developers to log activity within applications. The Apache Log4j vulnerable versions are versions 2.0 to version 2.14.1 inclusive. (updated: 2.15.0 was found with CVE-2021-45046 vulnerability)
- Because the Apache Log4j component was approved to be used by many manufactures, vendors, and software packages (such as Cisco, VMware, NetApp, Elastic Logstash, Docker, and more), Your IT environment might be vulnerable.
Were XPLG products affected by the Log4j vulnerability exploit?
- XPLG Products were not affected by the Log4J vulnerability exploit.
After an extensive security audit of the entire XPLG environment, we have found that none of the XPLG product suite systems contain the software identified in the vulnerability disclosure. (for both vulnerability found)
What security actions XPLG has taken?
- XPLG users do not need to take any immediate actions.
We have been working to assure the security of our environment since this Log4j vulnerability exploit was made public.
- XPLG Released Security Patch
Although this vulnerability ( update: including CVE-2021-45046 that was found in. Apache Log4j 2.15.0) does not compromise XPLG users, we are always committed to keeping our products’ security up to date. This security patch contains a secured Apache Log4j 2.16.0 version.
We strongly encourage you to review other applications for the Log4Shell vulnerability exploit in your IT environment and, if necessary, take immediate action.
- Find details about the latest Apache Log4j version, 2.17.0 published by Apache
Only if you can’t immediately install the latest Apache Log4J version, it was recommended to:
- Run the bypass (VR 2.1 and later)
Set True the following:
System-property log4j2.formatMsgNoLookups, or
- Remove the Class (VR 2 – 2.1)
JndiLookup from the classpath
Use the command:
zip -q -d log4j-core-*.jar org/apache/logging/log4j/core/lookup/JndiLookup.class