Log4j 2.17.0 and older Vulnerability on Siteminder SDK r12.8.x

Products

SITEMINDER

Issue/Introduction

A number of vulnerabilities were published for Apache Log4J version 2 impacting Log4j2 2.0-beta9 to 2.17.0

Siteminder bundles Apache Log4J2 in a number of components

r12.8.4: Log4j 2.10.0

r12.8.5: Log4j 2.12.1

r12.8.6: Log4j 2.12.1

r12.8.6a: Log4j 2.17.1

r12.8.7: Log4j 2.17.2

r12.8.8: Log4j 2.20.0

Environment

Component: Siteminder SDK

Versions: r12.8.4 - r12.8.6

Cause

CVE-2021-45046

SEVERITY: High

DESCRIPTION: Apache Log4j2 2.0-beta9 through 2.15.0 (excluding security releases 2.12.2, 2.12.3, and 2.3.1) 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 LDAP servers when message lookup substitution is enabled. From log4j 2.15.0, this behavior has been disabled by default. From version 2.16.0 (along with 2.12.2, 2.12.3, and 2.3.1), this functionality has been completely removed. Note that this vulnerability is specific to log4j-core and does not affect log4net, log4cxx, or other Apache Logging Services projects.

IMPACTED: Apache Log4j2 2.0-beta9 through 2.15.0 (excluding security releases 2.12.2, 2.12.3, and 2.3.1)

Remediated: Log4J 2.17.1

----------------------------------

CVE-2021-45046

SEVERITY: Critical

DESCRIPTION: It was found that the fix to address CVE-2021-44228 in Apache Log4j 2.15.0 was incomplete in certain non-default configurations. This could allows attackers 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) to craft malicious input data using a JNDI Lookup pattern resulting in an information leak and remote code execution in some environments and local code execution in all environments. Log4j 2.16.0 (Java 8) and 2.12.2 (Java 7) fix this issue by removing support for message lookup patterns and disabling JNDI functionality by default.

IMPACTED: Apache Log4j2 versions 2.0-alpha1 through 2.15.0

Remediated: Log4J 2.17.1

----------------------------------

CVE-2021-45105

SEVERITY: Medium

DESCRIPTION: Apache Log4j2 versions 2.0-alpha1 through 2.16.0 (excluding 2.12.3 and 2.3.1) did not protect from uncontrolled recursion from self-referential lookups. This allows an attacker with control over Thread Context Map data to cause a denial of service when a crafted string is interpreted. This issue was fixed in Log4j 2.17.0, 2.12.3, and 2.3.1.

IMPACTED: Apache Log4j2 versions 2.0-alpha1 through 2.16.0 (excluding 2.12.3 and 2.3.1)

Remediated: Log4J 2.17.1

----------------------------------

CVE-2021-44832

SEVERITY: Medium

DESCRIPTION: Apache Log4j2 versions 2.0-beta7 through 2.17.0 (excluding security fix releases 2.3.2 and 2.12.4) are vulnerable to a remote code execution (RCE) attack when a configuration uses a JDBC Appender with a JNDI LDAP data source URI when an attacker has control of the target LDAP server. This issue is fixed by limiting JNDI data source names to the java protocol in Log4j2 versions 2.17.1, 2.12.4, and 2.3.2.

IMPACTED: Apache Log4j2 versions 2.0-beta7 through 2.17.0 (excluding security fix releases 2.3.2 and 2.12.4)

Remediated: Log4J 2.17.1

----------------------------------

CVE-2021-4104

IMPACTED: Log4j 1.2

NOTE: This Vulnerability does not apply to Siteminder

Resolution

SiteMinder does not use JDBC Appender with a data source referencing a JNDI URL. As a result, CVE-2021-44832 does not impact SiteMinder.

Siteminder r12.8.6a upgrades Log4j2 to 2.17.1

Siteminder r12.8.7 upgrades Log4J2 to 2.17.2

Siteminder r12.8.8 upgrades Log4J2 to 2.20.0

If you are running on r12.8.4 - r12.8.6 and would rather upgrade Log4J to 2.17.1/2.17.2 on an existing, supported version of Siteminder, you can following these instructions:

Manually Updating Log4J2 to 2.17.1/2.17.2 on Siteminder SDK r12.8.6 and older

1) Download either log4j 2.17.1 or 2.17.2 jar files from the following Apache repository links:

Log4j 2.17.1 Downloads

log4j-api-2.17.1.jar

log4j-core-2.17.1.jar

log4j-slf4j-impl-2.17.1.jar

Log4j 2.17.2 Downloads (Optional)

log4j-api-2.17.2.jar

log4j-core-2.17.2.jar

log4j-slf4j-impl-2.17.2.jar

2) Backup of the existing Log4j2 files in your environment from the following locations:

<sdk_installation_path>\java\log4j-api-2.17.1.jar

<sdk_installation_path>\java\log4j-core-2.17.1.jar

<sdk_installation_path>\java\log4j-slf4j-impl-2.17.1.jar

3) Delete the existing log4j files from the above-mentioned location.

4) Copy the Log4j 2.17.1 files to the server and place the new jars in the following location:

<sdk_installation_path>\java\log4j-api-2.17.1.jar

<sdk_installation_path>\java\log4j-core-2.17.1.jar

<sdk_installation_path>\java\log4j-slf4j-impl-2.17.1.jar

5) Update all the references of the existing 2.x log4j version with the 2.17.1/2.17.2 version in the class path parameter of all the custom applications that are built using SDK, and save the changes.

6) Restart the custom applications.