RHSA-2021:5130: Critical: Red Hat Integration Camel-K 1.6.2 release and security update
A minor version update (from 1.6.1 to 1.6.2) 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 in Log4j 2.x when logs contain an attacker-controlled string value (CVE-2021-44228)</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
Remediation
Event History
Frequently Asked Questions
What is the severity of RHSA-2021:5130?
The severity of RHSA-2021:5130 is classified as critical due to the remote code execution vulnerability in Log4j 2.x.
How do I fix RHSA-2021:5130?
You can fix RHSA-2021:5130 by upgrading to the latest version of Red Hat Camel K, which has been patched for the vulnerabilities.
Which versions of Red Hat Camel K are affected by RHSA-2021:5130?
Red Hat Camel K versions prior to 1.6.2 are affected by RHSA-2021:5130.
What kind of vulnerabilities are addressed in RHSA-2021:5130?
RHSA-2021:5130 addresses a remote code execution vulnerability in log4j-core.
Is there a workaround for RHSA-2021:5130?
There are no specific workarounds for RHSA-2021:5130; updating to the patched version is recommended.