CVE-2021-44228

Отчет

This issue only affects log4j versions between 2.0 and 2.14.1. In order to exploit this flaw you need:

• A remotely accessible endpoint with any protocol (HTTP, TCP, etc) that allows an attacker to send arbitrary data,
• A log statement in the endpoint that logs the attacker controlled data. In Red Hat OpenShift Logging the vulnerable log4j library is shipped in the Elasticsearch components. Because Elasticsearch is not susceptible to remote code execution with this vulnerability due to use of the Java Security Manager and because access to these components is limited, the impact by this vulnerability is reduced to Moderate. As per upstream applications using Log4j 1.x may be impacted by this flaw if their configuration uses JNDI. However, the risk is much lower. This flaw in Log4j 1.x is tracked via https://access.redhat.com/security/cve/CVE-2021-4104 and has been rated as having Moderate security impact. CodeReady Studio version 12.21.1 was released containing a fix for this vulnerability. The following products are NOT affected by this flaw and have been explicitly listed here for the benefit of our customers.
• Red Hat Enterprise Linux
• Red Hat Advanced Cluster Management for Kubernetes
• Red Hat Advanced Cluster Security for Kubernetes
• Red Hat Ansible Automation Platform (Engine and Tower)
• Red Hat Certificate System
• Red Hat Directory Server
• Red Hat Identity Management
• Red Hat CloudForms
• Red Hat Update Infrastructure
• Red Hat Satellite
• Red Hat Ceph Storage
• Red Hat Gluster Storage
• Red Hat OpenShift Data Foundation
• Red Hat OpenStack Platform
• Red Hat Virtualization
• Red Hat Single Sign-On
• Red Hat 3scale API Management

Меры по смягчению последствий

For Log4j versions >=2.10 set the system property log4j2.formatMsgNoLookups or the environment variable LOG4J_FORMAT_MSG_NO_LOOKUPS to true For Log4j versions >=2.7 and <=2.14.1 all PatternLayout patterns can be modified to specify the message converter as %m{nolookups} instead of just %m For Log4j versions >=2.0-beta9 and <=2.10.0 remove the JndiLookup class from the classpath. For example:

On OpenShift 4 and in OpenShift Logging, the above mitigation can be applied by following the steps in this article: https://access.redhat.com/solutions/6578421 On OpenShift 3.11, mitigation to the affected Elasticsearch component can be applied by following the steps in this article: https://access.redhat.com/solutions/6578441