CVE-2021-44832 - Remote Code Execution (RCE)
Severity: Low2021-12-29
Abstract
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 where an attacker with permission to modify the logging configuration file can construct a malicious configuration using a JDBC Appender with a data source referencing a JNDI URI which can execute remote code. 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.
The Oxygen XML products incorporate the Apache Log4j2 as a third-party library. This advisory was opened to address the potential impact of this third-party library vulnerability.
Affected Products/Versions
Product | Severity | Fixed Release Availability |
Oxygen Content Fusion v4.1 and older versions | Low | N/A |
Oxygen XML Web Author from 22.1.0 to 24.0.0 | Low | Oxygen XML Web Author v24.0.0.4 build 2022020109 |
Oxygen Feedback 2.0 and older | Low | N/A |
Oxygen XML Publishing Engine from v22.1 to v24.0 | Low | Oxygen XML Publishing Engine v24.0 build 2022012805 |
Oxygen XML WebHelp from v22.1 to v24.0 | Low | Oxygen XML WebHelp v24.0 build 2022011710 |
Oxygen PDF Chemistry from v22.1 to v24.0 | Low | Oxygen PDF Chemistry v24.0 build 2022012805 |
Oxygen License Server from v22.1 to v24.0 | Low | Oxygen License Server v24.0 build 2022020113 |
Oxygen XML Author from v16.1 to v24.0 | Low | Oxygen XML Author v24.0 build 2022012607 |
Oxygen XML Developer from v16.1 to v24.0 | Low | Oxygen XML Developer v24.0 build 2022012607 |
Oxygen XML Editor from v16.1 to v24.0 | Low | Oxygen XML Editor v24.0 build 2022012607 |
Mitigation
- If you are using an older version of Oxygen XML Editor/Author/Developer/Web Author, use the oxygen-log4j-patcher.
- If you are using Oxygen Content Fusion, use the content-fusion-log4j-patcher.
- For other scenarios, manually update all occurrences of log4j-core to version 2.17.1.
Detail
CVE-2021-44832
Severity: Medium
CVSS Score: 6.6
The Apache Log4j2 third-party library used by Oxygen XML products is an affected version mentioned in CVE-2021-44832 vulnerability description. However, our default configuration does not use JDBC Appender with a data source referencing a JNDI URI and can be only exploited by modifying the logging configuration by a trusted party. For that reason, we have rated the severity level for our products as low.
Revision History
2022-02-04 Starting with Oxygen XML Web Author 24.0.0.4 build 2022020109, the Apache Log4j library
was updated to version 2.17.1. This version is not affected anymore by this vulnerability.
Starting with Oxygen License Server 24.0 build 2022020113, the Apache Log4j library
was updated to version 2.17.1. This version is not affected anymore by this vulnerability.
2022-01-31 Starting with Oxygen XML Author 24.0 build 2022012607, the Apache Log4j library
was updated to version 2.17.1. This version is not affected anymore by this vulnerability.
Starting with Oxygen XML Developer 24.0 build 2022012607, the Apache Log4j library
was updated to version 2.17.1. This version is not affected anymore by this vulnerability.
Starting with Oxygen XML Editor 24.0 build 2022012607, the Apache Log4j library
was updated to version 2.17.1. This version is not affected anymore by this vulnerability.
Starting with Oxygen XML WebHelp 24.0 build 2022011710, the Apache Log4j library
was updated to version 2.17.1. This version is not affected anymore by this vulnerability.
Starting with Oxygen PDF Chemistry 24.0 build 2022012805, the Apache Log4j library
was updated to version 2.17.1. This version is not affected anymore by this vulnerability.
Starting with Oxygen XML Publishing Engine 24.0 build 2022012805, the Apache Log4j library
was updated to version 2.17.1. This version is not affected anymore by this vulnerability.
2022-01-19 Add recommendation to use the oxygen-log4j-patcher and content-fusion-log4j-patcher as mitigation.