GIGABYTE Server Management (GSM) Software Updates for Apache Log4j Security Vulnerabilities

CVE-2021-44228, CVE-2021-45046, CVE -2021-45105

CVE-2021-44228, CVE-2021-45046, CVE -2021-45105
Dec 22, 2021

Updated 2021/12/27: GSM Agent version 2.3 is now available


GIGABYTE is aware of the recently disclosed Apache Log4j 2 (version 2.0 to 2.14.1) security vulnerabilities (CVE-2021-44228). If exploited, this vulnerability allows adversaries to potentially take full control of the impacted system. Therefore, we have released the software updates to mitigate risk of these vulnerabilities on our products as details can be found below.

 

Common Vulnerabilities or Exposures (CVEID):  CVE-2021-44228

Severity Rating (CVSS): 10.0, Critical

Description: 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.

 

Common Vulnerabilities or Exposures (CVEID):  CVE-2021-45046

Severity Rating (CVSS): 9.0, 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 allow 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.

 

Common Vulnerabilities or Exposures (CVEID):  CVE-2021-45105

Severity Rating (CVSS): 7.5, High

Description: 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.

 

GIGABYTE is releasing software updates to fix these vulnerabilities. The affected products, their software update availability and release schedule are listed in the table below. 

 

Affected GIGABYTE’s Software/Firmware

Fixed Version & Availability

CVE-2021-44228

CVE-2021-45046

CVE-2021-45105

BMC firmware

Not affected*

GSM Server

Version 2.08 (Available)

GSM Agent

Version 2.3  (Available)

*Refer to AMI Customer Advisory Document: AMI_MegaRAC_SPx_CVE-2021-144228

Please navigate to the "Support->Utility" section of the relevant product page to download the updated software when available.

For any further assistance regarding this issue please contact your GIGABYTE sales representative, or create a new support ticket at https://esupport.gigabyte.com