Oxygen XML Editor
The Premier All-In-One XML Editing Suite
Oxygen XML Author
Single-Source XML Authoring and Multi-Channel Publishing
Oxygen XML Developer
The Required Tools for Designing XML Schemas and Transformation Pipelines
Oxygen JSON Editor
The Perfect Tool to Simplify Your JSON Editing Experience
Oxygen Publishing Engine
The Complete DITA Publishing Solution for WebHelp and PDF Output
Oxygen PDF Chemistry
Chemistry Converts HTML and XML to PDF Using CSS
Oxygen XML WebHelp
Publish DITA and DocBook Content to WebHelp Output
Oxygen Styles Basket
Customize the Look and Feel of Your PDF and WebHelp Output
Oxygen XML Web Author
Engage Your Whole Organization In Content Creation
Oxygen Content Fusion
The Web-based Collaboration Platform to Craft Tomorrow's Content
Oxygen Feedback
Modern Commenting Platform
Cloud
Enterprise
Oxygen AI Positron
Enhance Your Productivity with the Power of AI
Oxygen Scripting
Automate and Run Oxygen Utilities from the Command-Line Interface
Oxygen SDK
Specifically designed for application developers and integrators
Shop
Pricing and licensing for businesses, Academic and individuals
Severity: Low2021-12-29
Security Advisories
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.
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.
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.
List of Security Advisories