Skip to main content

SolarWinds Releases Security Updates and Remediation Actions for SolarWinds Database Performance Analyzer

SolarWinds have released a security update to address the Log4Shell vulnerability in their Database Performance Analyzer product.

Threat ID:
CC-3998
Threat Severity:
Information only
Published:
23 December 2021 2:19 PM
Report a cyber attack: call 0300 303 5222 or email [email protected]

Summary

SolarWinds have released a security update to address the Log4Shell vulnerability in their Database Performance Analyzer product.

Affected platforms

The following platforms are known to be affected:

Versions: DPA 2021.1.x, DPA 2021.3.x and DPA 2022.1 RC1

Database Performance Analyzer

Threat details

Introduction

SolarWinds have released security updates to address the Log4Shell vulnerabilities in their Database Performance Analyzer software. An unauthenticated remote attacker could exploit these vulnerabilities to take control of affected systems.

Remediation advice

Affected organisations are encouraged to review the SolarWinds Database Performance Analyzer article Database Performance Analyzer (DPA) and the Apache Log4j Vulnerability and apply any relevant updates or remediation actions.

Definitive source of threat updates

CVE Vulnerabilities

Status Published

CVE-2021-44228

Apache Log4j2 2.0-beta9 through 2.12.1 and 2.13.0 through 2.15.0 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, 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.
Status Published

CVE-2021-45046

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.
Status Published

CVE-2021-45105

Apache Log4j2 versions 2.0-alpha1 through 2.16.0 (excluding 2.12.3) 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 and 2.12.3.

Last edited: 23 December 2021 3:32 pm