First published: Thu Jan 20 2022(Updated: )
A minor version update (from 1.6.2 to 1.6.3) is now available for Red Hat Camel K that includes bug fixes and enhancements, which are documented in the Release Notes document linked to in the References.<br>Security Fix(es):<br><li> log4j-core: remote code execution via JDBC Appender (CVE-2021-44832)</li> <li> log4j-core: DoS in log4j 2.x with thread context message pattern and context lookup pattern (incomplete fix for CVE-2021-44228) (CVE-2021-45046)</li> <li> log4j-core: DoS in log4j 2.x with Thread Context Map (MDC) input data contains a recursive lookup and context lookup pattern (CVE-2021-45105)</li> For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.
Affected Software | Affected Version | How to fix |
---|---|---|
Red Hat Camel K |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of RHSA-2022:0223 is classified as critical due to the risk of remote code execution via JDBC Appender.
To fix RHSA-2022:0223, you must update Red Hat Camel K from version 1.6.2 to 1.6.3 or apply the recommended patches.
RHSA-2022:0223 impacts Red Hat Camel K that utilizes log4j-core.
The main changes in RHSA-2022:0223 include bug fixes and enhancements as documented in the release notes.
There is no recommended workaround for RHSA-2022:0223; updating to the fixed version is advised.