Summary
about Log4J Security Threat:
On Dec. 9, 2021, a
remote code execution (RCE) vulnerability Apache log4j
2 was identified being exploited in the wild. Public proof of
concept (PoC) code was released and subsequent investigation revealed that
exploitation was incredibly easy to perform. By submitting a specially crafted
request to a vulnerable system, depending on how the system is configured, an
attacker is able to instruct that system to download and subsequently execute a
malicious payload. Due to the discovery of this exploit being so recent, there
are still many servers, both on-premises and within cloud environments, that
have yet to be patched. Like many high severity RCE exploits, thus far, massive
scanning activity for CVE-2021-44228 has begun on the internet with the intent
of seeking out and exploiting unpatched systems. We highly recommend that organizations
upgrade to the latest version (2.15.0-rc2) of Apache log4j 2 for all systems.
Description of the Vulnerability
(CVE-2021-44228)
The
Apache log4j library allows for developers to log various data within their
application. In certain circumstances, the data being logged originates from
user input. Should this user input contain special characters and be
subsequently logged within the context of log4j, the Java method lookup will finally be called to execute the
user-defined remote Java class in the LDAP server. This will in turn lead to
RCE on the victim server that uses the vulnerable log4j 2 instance.
Affected Version
Apache
Log4j 2.x <= 2.15.0-rc1
Log4J 1.x version and slf4j
version are not affected.
Affected Software
A
significant number of Java-based applications are using log4j as their logging
utility and are vulnerable to this CVE. To the best of our knowledge, at least
the following software may be impacted:
- Apache Struts
- Apache Solr
- Apache Druid
- Apache Flink
- ElasticSearch
- Flume
- Apache Dubbo
- Logstash
- Kafka
- Spring-Boot-starter-log4j2
Root Cause Analysis
If we
take a closer look, we discover that log4j 2.x supports a mechanism called lookups, which is usually used to set up the log4j
config flexibly for users. The official introduction about Lookups is as
follows:
Lookups provide a way to add values to the log4j configuration
at arbitrary places. They are a particular type of Plugin that implements the
StrLookup interface.
The
normal user can conveniently and flexibly add values to the configuration at
arbitrary places with the predesigned format by using this feature. In detail,
when calling the log method in the application, log4j 2.x will call the format
method to check the specific characters ${ in
each log.
Should
these characters be present, the Java method lookup will be called to find strings after
the characters ${ and
then replace the expression after the characters ${ with the real value found before. For example, when
calling the log function in the application to log the content shown in Figure
1, the strings java:runtime, java:vm, and java:os after
the characters ${ will
be considered as the parameter of the lookup method
and finally replaced with the corresponding values, such as Java(TM) SE Runtime Environment (build 1.7.0_67-b01) from Oracle
Corporation, Java
HotSpot(TM) 64-Bit Server VM (build 24.65-b04, mixed mode, and Windows 7 6.1 Service Pack 1, architecture: amd64-64.
Exploit
Exploit
code for the CVE-2021-44228 vulnerability has been made publicly available. Any
user input hosted by a Java application using the vulnerable version of log4j
2.x may be exposed to this attack, depending on how logging is implemented
within the Java application. We have seen publicly reported allegedly
successful attacks targeting iCloud, Twitter, Amazon, Baidu, and Minecraft.
Permanent Fix
Upgrade your log4j version to 2.15 which is recently launched to fix this issue.
As
a workaround you can also try below .
• Modify every logging pattern layout to say
%m{nolookups} instead of %m in your logging config files (here are Apache’s details);
or,
• Users should switch log4j2.formatMsgNoLookups to true by adding:”‐Dlog4j2.formatMsgNoLookups=True” to the JVM command for starting the application.
Comments
Post a Comment