ThreatConnect is actively following the security vulnerability in the open-source Apache “Log4j 2″ utility (CVE-2021-44228, CVE-2021-45046, CVE-2021-45105 (reported on December 18)). We are also aware of the reported Apache “Log4j 1.x” vulnerability (CVE-2021-4104).

We are actively analyzing the impact of these vulnerabilities to the ThreatConnect products and communicating directly with customers via email announcements. Please reach out to your ThreatConnect Customer Success Manager or email success@threatconnect.com if you have not received these announcements or have any questions related to this advisory.

Background: The Apache Log4j 2 utility is a commonly used component for logging requests. On December 9, 2021, a vulnerability was reported that could allow a system running Apache Log4j 2 version 2.15 or below to be compromised and allow an attacker to execute arbitrary code.

On December 10, 2021, NIST published a critical Common Vulnerabilities and Exposure alert, CVE-2021-44228. More specifically, Java Naming Directory Interface (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 remote servers when message lookup substitution is enabled.