RHSA-2022:5101: Important: Red Hat AMQ Broker 7.10.0 release and security update
AMQ Broker is a high-performance messaging implementation based on ActiveMQ Artemis. It uses an asynchronous journal for fast message persistence, and supports multiple languages, protocols, and platforms. <br>This release of Red Hat AMQ Broker 7.10.0 serves as a replacement for Red Hat AMQ Broker 7.9.4, and includes security and bug fixes, and enhancements. For further information, refer to the release notes linked to in the References section.<br>Security Fix(es):<br><li> nodejs-lodash: prototype pollution in defaultsDeep function leading to modifying properties (CVE-2019-10744)</li> <li> amq: AMQ Broker Operator ClusterWide Edit Permissions Due Token Exposure (CVE-2022-1833)</li> <li> jackson-databind: denial of service via a large depth of nested objects (CVE-2020-36518)</li> <li> AMQ Broker: Malformed message can result in partial DoS (OOM) (CVE-2021-4040)</li> <li> netty: control chars in header names may lead to HTTP request smuggling (CVE-2021-43797)</li> <li> artemis-commons: Apache ActiveMQ Artemis DoS (CVE-2022-23913)</li> <li> springframework: Spring Framework: Data Binding Rules Vulnerability (CVE-2022-22968)</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-2022:5101?
The severity of RHSA-2022:5101 is classified as important.
How do I fix RHSA-2022:5101?
To fix RHSA-2022:5101, update to the latest version of Red Hat AMQ Broker as recommended in the advisory.
Which systems are affected by RHSA-2022:5101?
RHSA-2022:5101 affects Red Hat AMQ Broker 7.10.0 and possibly earlier versions.
What are the consequences of not addressing RHSA-2022:5101?
Not addressing RHSA-2022:5101 may expose the system to security vulnerabilities and operational risks.
Is there a workaround for RHSA-2022:5101?
There are no official workarounds for RHSA-2022:5101; updating the software is the recommended solution.