SB2021121647 - OpenShift Container Platform 4.6 update for log4j
Published: December 16, 2021 Updated: April 14, 2025
Breakdown by Severity
- Low
- Medium
- High
- Critical
Description
This security bulletin contains information about 3 secuirty vulnerabilities.
1) Code Injection (CVE-ID: CVE-2021-44228)
The vulnerability allows a remote attacker to execute arbitrary code on the target system.
The vulnerability exists due to improper input validation when processing LDAP requests. A remote attacker can send a specially crafted request to the application and execute arbitrary code on the target system.
Successful exploitation of this vulnerability may result in complete compromise of vulnerable system.
Note, we are aware of attackers exploiting the vulnerability in the wild.
2) Code Injection (CVE-ID: CVE-2021-45046)
The vulnerability allows a remote attacker to compromise the affected system.
The
vulnerability exists due to incomplete patch in Apache Log4j 2.15.0 for
a code injection vulnerability #VU58816 (CVE-2021-44228) in certain
non-default configurations. A remote attacker with control over Thread
Context Map (MDC) input data when the logging configuration uses a
non-default Pattern Layout with either a Context Lookup (for example,
$${ctx:loginId}) or a Thread Context Map pattern (%X, %mdc, or %MDC) can
pass malicious data using a JNDI Lookup pattern and perform a denial of
service (DoS) attack, exfiltrate data or execute arbitrary code.
Later discovery demonstrates a remote code execution on macOS but no other tested environments.
3) Deserialization of Untrusted Data (CVE-ID: CVE-2021-4104)
The vulnerability allows a remote attacker to execute arbitrary code on the target system.
The vulnerability exists due to insecure input validation when processing serialized data in JMSAppender, when the attacker has write access to the Log4j configuration. The attacker can provide TopicBindingName and TopicConnectionFactoryBindingName configurations causing JMSAppender to perform JNDI requests that result in remote code execution.
Note this issue only affects Log4j 1.2 when specifically configured to
use JMSAppender, which is not the default.
Remediation
Install update from vendor's website.