Critical Vulnerability Alert: Log4j
This page will be updated as additional information is released.
Last Updated: December 20, 12:00pm EST
On December 10, National Institute of Standards and Technology (NIST) issued a Common Vulnerabilities and Exposures (CVE) for a vulnerability in Log4j. This vulnerability when exploited can lead to the attacker having the ability to run code remotely. This vulnerability is even more critical because there are active exploits available and being run across the Internet, including mass scans for vulnerable systems. The vulnerability is being tracked with NIST CVE-2021-44228.
Log4j is a Java framework/package that is used to help with application logging of Java applications. By using this framework, you can output log messages from the Java application without changing the application’s binary package. This allows for easier logging and especially debugging of Java applications. It is used widely in both open source and commercial web interfaces and applications. This widespread use contributes to the severity of this vulnerability. It is important to note that many of the logs that Log4j is processing are application-specific (in many cases debug) logs and so they are probably not being sent to security intelligence event management (SIEM) systems.
Since the announcement of the CVE, Apache has released multiple patches to address the vulnerability directly. Many applications have also released an updated version to address the vulnerability in their specific products. You can see the list below of the resources that Nexum is putting together to help you find any systems that may be affected. In addition, the Nexum SNOCC is working directly with our managed services customers to help them detect and block remote exploits.
GitHub Scanner Repo – https://gist.github.com/Neo23x0/e4c8b03ff8cdf1fa63b7d15db6e3860b
Nexum Technology Partner Responses
Palo Alto Networks – https://security.paloaltonetworks.com/CVE-2021-44228