Red Hat Security Advisory: Red Hat Integration Camel-K 1.6.2 release and security update
🔗 CVE IDs covered (1)
📋 Description
CVE-2021-44228 — log4j-core: Remote code execution in Log4j 2.x when logs contain an attacker-controlled string value
🎯 Affected products1
- Red Hat Integration
✅ Remediation
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 Workaround: For Log4j versions >=2.10 set the system property log4j2.formatMsgNoLookups or the environment variable LOG4J_FORMAT_MSG_NO_LOOKUPS to true For Log4j versions >=2.7 and <=2.14.1 all PatternLayout patterns can be modified to specify the message converter as %m{nolookups} instead of just %m For Log4j versions >=2.0-beta9 and <=2.10.0 remove the JndiLookup class from the classpath. For example: ``` zip -q -d log4j-core-*.jar org/apache/logging/log4j/core/lookup/JndiLookup.class ``` On OpenShift 4 and in OpenShift Logging, the above mitigation can be applied by following the steps in this article: https://access.redhat.com/solutions/6578421 On OpenShift 3.11, mitigation to the affected Elasticsearch component can be applied by following the steps in this article: https://access.redhat.com/solutions/6578441
🔗 References (7)
- selfhttps://access.redhat.com/errata/RHSA-2021:5130
- externalhttps://access.redhat.com/security/updates/classification/#critical
- externalhttps://access.redhat.com/jbossnetwork/restricted/listSoftware.html?downloadType=distributions&product=red.hat.integration&version=2021-Q4
- externalhttps://access.redhat.com/documentation/en-us/red_hat_integration/2021.q4
- externalhttps://access.redhat.com/security/vulnerabilities/RHSB-2021-009
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2030932
- selfhttps://security.access.redhat.com/data/csaf/v2/advisories/2021/rhsa-2021_5130.json